Integration Azure DevOps with DevOps Change Velocity

[Francisco Sandi]

I'm trying to deploy ADO with DevOps Change Velocity, but I'm getting an error saying "The callback cannot be processed because the orchestration tool cannot be notified." implement stage but in ADO the notification never arrives so the stage does not advance and is left waiting, I attach screenshots of the tests, if they will take up more time please tell me.

Error

devopsErrorCode: REST_CALL_ERROR

internalMsg:  Unknown error

errorSources: ["DevOpsADOPToolIntegrationHandler.notifyWithCallback","DevOpsADOPToolIntegrationHandler.notifyWithCallback","Flow action - DevOps - Notify Orchestration Tool with Change Decision","Flow - Change Control Callback"]

properties: {"REST_STATUS_CODE":203,"REST_ERROR_CODE":0,"ALIAS_ID":"af7fdb791b5f8e54ffbe0dc8cc4bcbcd"}

[Community Alums]

Hi Francisco, have you managed to find the root cause for that error? 

We came across to the same one and still struggling to identify why it happens. I hope I'll have some useful update soon to share it here.

BR,
Alexander

[Francisco Sandi]

Hello I have good news, I was able to solve the problem, the first thing we did was that the script include RiskCalculator, it was put in a way that all areas can access it

Francisco Sandi

[Bartosz Glowac1]

We had the same issue as you described.

I could not associate it with the RiskCalculator as it was mentioned by you @Francisco Sandi so I dropped this direction.

I was exploring the issue further and found that the error comes from the flow "Change Control Callback" which could not successfully execute action "DevOps - Notify Orchestration Tool with Change Decision" .

I have tried to run this action separately in a test mode in Flow designer providing all the input data that were normally used within unsuccessful execution of "Change Control Callback" flow. When action was executed in this way it did work properly, updated callback and allowed the process to continue.

Having that in mind, I went to the  "Change Control Callback" flow, I opened Properties and set: Run as = "System User".

From that moment everything runs well, "DevOps - Notify Orchestration Tool with Change Decision" action completes well with no error anymore.

It seems that some customization in our system caused that usual setting of "User who initiates the session" with sn_devops.admin role was not sufficient to execute this action but System User is strong enough to execute everything as it should be.

I know it is a long time since the questions were asked but I believe this solution may be useful for somebody in the future.

Best regards,

Bartosz