Runbook got failed but data factory webhook activity kept running or completed without any error

Ravi Shukla 21

Hello Team , We have create runbook which process the azure analysis services .and we using data factory webhook activity to trigger the runbook . For success scenario :- once runbook completed without error webhook completed . For failure scenario:- once runbook completed and we have error on error tab but webhook still getting completed ,Please find the screen shot below :- Runbook error:-![128870-image.png][1] ADF wehbook:-![128943-image.png][2] Runbook ![128905-image.png][3] We need if Runbbok have error then webhook should failed on adf . [1]: /api/attachments/128870-image.png?platform=QnA [2]: /api/attachments/128943-image.png?platform=QnA [3]: /api/attachments/128905-image.png?platform=QnA

ShaikMaheer-MSFT 37,896 Reputation points Microsoft Employee

2021-09-06T05:20:53.837+00:00

Hi anonymous user ,

Thank you for posting query on Microsoft Q&A Platform.

Could you please see what output json of webhook activity giving in case of failure scenario?

You can check the status returned to webhook activity in the output json and then using if activity validate the status and control pipeline in desired fashion.

Also, WebHook activity now allows you to surface error status and custom messages back to activity and pipeline. Set reportStatusOnCallBack to true, and include StatusCode and Error in callback payload. For more information, Click here.

Please note, The webhook activity fails when the call to the custom endpoint fails. Any error message can be added to the callback body and used in a later activity.

Please let us know updates so that we can check further. Thank you.
ShaikMaheer-MSFT 37,896 Reputation points Microsoft Employee

2021-09-13T09:59:14.823+00:00

Hi anonymous user ,

Following up to see if below answer helps you? If yes, Please consider to click on Accept Answer. Accepted answers helps community as well. Please let us know if any further queries. Thank you.

1 answer

Stanislav Zhelyazkov 21,336 Reputation points MVP

2021-09-03T07:44:25.67+00:00

Hi,
The answer to this issue is available here. If a cmdlet gives error and you want the runbook to fail instead of continuing to the next cmdlet you need to $errorActionPreference = "Stop" by default that value is Continue.

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.
Please sign in to rate this answer.
Ravi Shukla 21 Reputation points

2021-09-03T08:55:50.817+00:00

Hello Stan, I had tried the answer given by you . post applied try and catch statement on automation script my runbook is getting failed but still my ADF pipeline still running .please find the screenshot below :- Runbook:-![129091-image.png][1] ADF pipeline still running:-![129048-image.png][2] while applying try and catch statement my runbook got failed but why my ADF pipeline still running . Please let me know if you need any information. [1]: /api/attachments/129091-image.png?platform=QnA [2]: /api/attachments/129048-image.png?platform=QnA

Ravi Shukla 21 Reputation points

2021-09-03T09:10:50.153+00:00

Hi Stan ,

I am able to get the failure on runbook now ,but still my ADF pipeline is kept running .Please suggest

I am using webhook activity to trigger the runbook .

Please let me know if you need any other details .

Stanislav Zhelyazkov 21,336 Reputation points MVP

2021-09-03T09:31:36.54+00:00

Hi,
From this point on is is about building your runbook (code) logic as you desire. When a webhook for a runbook is called it just triggers the runbook but does not wait for end result. That is just general behavior of any service that has webhook. If you want to achieve something else and the behavior is not the one you are seeking you will probably have to go on another path. You should accept the answer given and may be post another question specific for ADF on what you are trying to achieve.

Stanislav Zhelyazkov 21,336 Reputation points MVP

2021-09-07T08:52:17.723+00:00

See my previous comment.
Sign in to comment