Logic App workflow run is marked as "Failed" because on action fails, even though dependent actions succeed

SriRaghavendran Prabhakaran 300 Reputation points
2024-05-17T10:27:46.3533333+00:00

Hello Team,

Our workflow having Multiple SMTP connectors to handle 429 errors. basically , if there is a failure in a connector redirection is based on status code to next SMTP connector.

The above logic helped us in achieve functionally but we notice any one failure of SMTP indicates the entire workflow as failure and that not the real case because it is getting successful in another SMTP connector. we want to make the workflow to success if any of the SMTP connector get successful. Let us know on that and attached a screen shot for your reference.

User's image

Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
2,940 questions
{count} votes

Accepted answer
  1. LeelaRajeshSayana-MSFT 13,951 Reputation points
    2024-05-17T16:26:17.7733333+00:00

    Hi @SriRaghavendran Prabhakaran Thank you for posting question on this forum and letting us know about your use case.

    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. To overcome this, you can take advantage of merging the branches and form an action that gets triggered based on different outcome scenarios from preceding parent action.

    When you click an action in the workflow, you can find a Settings tab which will let you choose the Run After Actions which can trigger your action. It further lets you choose which status of the parent action can trigger it. Please find the below image for your reference.

    User's image

    Here, I have selected my ***Compose ***action to Run after Send Email and Set Variable action and irrespective of the outcome of these actions, my Compose action gets triggered. Here is a reference of how my logic app looks like.

    User's image

    Please refer the following run time history instance which shows a Runtime status as Successful even when there is a failed action item in the flow.

    enter image description here

    Inspect your runtime history and identify which branch ends in fail state and try to merge action. Here is a document you can refer for more details on Join parallel branches in Logic App.

    Please be cautious when you are taking this approach as you might accidentally cause False positives and miss capturing failed events. Please let us know if you have any questions or need further assistance in the comments below.


    If the response helped, please do click Accept Answer and Yes for the answer provided. Doing so would help other community members with similar issue identify the solution. I highly appreciate your contribution to the community.

    2 people found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful