I have a Web activity that performs a GET operation to an endpoint. I have set it up to do something On Failure (which works just fine) and another set of action upon Success. But this last part gets skipped entirely even though the output of the Web action is Succeeded.
Here is shown the succeeded status and my config
enter image description here
I tried removing and re-adding the On Success connector, but yielded no different results.
Based on your flow, it would never proceed ahead:
Because as per your logic to proceed to the Set run time, Web activity 1 AND Web activity 2 should be success but that can never be the case since web activity 2 can be a success only if web activity 1 has failed thereby not proceeding further.
The below blog explains how to handle this :
https://datasharkx.wordpress.com/2021/08/19/error-logging-and-the-art-of-avoiding-redundant-activities-in-azure-data-factory/
Both dependencies of set runtime status cannot end as succeeded. You need to use a combination of skipped/completed states: https://learn.microsoft.com/en-us/azure/data-factory/tutorial-pipeline-failure-error-handling
From the pipeline image , I think it should move on with success .
Can you please cross check what is status code of web activity and is it returning something back ? Is the status code be 2xx ? If I were you could have tried to check with the "Upon Completion" option and see it works .
Related
I am triggering a Pipeline from another Pipeline over REST API, which works fine but one thing is annoying me.
I could not find a way to display with queued Pipeline original Commit Message of the Triggering pipeline.
There is a build in variable '$(Build.SourceVersionMessage)' which contains the information I need but I could not find a way to pass this information to triggered workflow so it can be displayed.
Following fields existing the REST API, I though the correct field would be 'triggerInfo' but that didn't changed anything in displayed build message.
Any idea how can I transfer this information and display it?
I am writing an automation routine that will include manually running a GitHub Workflow. I need to monitor the status of the workflow and download the logs once it’s finished.
Everything is fairly straightforward. The only missing link in the chain is how to determine the run ID for the workflow that I just invoked. There is no information that comes back from the REST API call (/repos/{owner}/{repo}/actions/workflows/{workflow_id}/dispatches endpoint) in either the body or the headers that gives me that information.
How can I determine what the run ID is for the workflow when it is invoked?
I tried to use the PowerShell sample https://learn.microsoft.com/en-us/azure/azure-monitor/platform/data-collector-api#powershell-sample without any changes.
It completes with status 200 (OK) and correctly creates a new table with LogType (MyRecordType) within the Custom Logs in the portal (Log Analytics Workspace->Logs).
However, the events that are submitted don't turn up there - there are always "No results from the last 24 hours". Also, within the new table, none of the custom properties are created.
Has anybody observed a similar problem? (Some people seem to be using the C# code successfully.) Thanks!
Crazy... on the next day, all the events had turned up in the Log Analytics workspace. Even new events that I generated turned up immediately.
It seems this was a glitch just on that day. Well, the API is in "preview"...
Within LogicApp I have a parallel branch with run afer set to when fail. If the previous step fails, appropriate actions are taken to mitigate the situation and no more action is needed, nor information on the fail. From business and user perspective that is success, so final Status for the whole LogicApp run shall be Succeeded instead of Failed.
How can I change the LogicApp status to Succeeded?
Or revoke a fail status for particular action (so assume this will solve the problem as well), when I know that it has been mitigated?
This is because the logic apps the engine determines the entire run's status by evaluating all the branch statuses. If any branch ends in failure, the entire logic app run is marked Failed.
The simplest way is add an action after the parallel like the below to add action run after both is successful and is skipped. Cause you already set the parallel action to handle the error and only one branch could be skipped, and with this setting even one branch gets exception failed the logic app still could return fail.
The last action could be any in my test I use a response action, make sure this action will success. And the below is my test, one only one action fail but only one branch is skipped one with one branch failed.
Update with terminate: Check my setting for terminate.
I want to track status code of a entire logic app instead of particular action status code using expression.
Status Code would be mention in tracked properties of a logic app.
Any help?
You can check status using below expression code
#int(actionOutputs('ActionName').statusCode)
Then you can check that code using condition like in below picture
If You have any more questions related to feel free to ask
you can track entire logic app staus using Operations Management Suite (OMS) and Log Analytics
its give you entire logic app in details status please check below link
Please check for OMS details
Stay tuned. In a couple of days, I will be publishing an article on how to know the status of a running Logic App. Will update this Answer once it's posted.
And it's here:
Knowing the State of Your Logic App Process