Logic App Workflow (Standard) Tasks
  • 02 Sep 2022
  • 1 Minute to read
  • Contributors
  • Dark
  • PDF

Logic App Workflow (Standard) Tasks

  • Dark
  • PDF


A failed Logic App Workflow (Standard) run can be resubmitted at some point in time which might result in a successful run.

Serverless360 provides the capability to automate the process of resubmitting the failed Logic App Workflow (Standard) runs.

Resubmitting failed Workflow runs

The Automated task can be configured to resubmit only the runs that are required by using the following filters:

  • Failure Occurrence: The Logic App Workflow (Standard) runs failed in the past x minutes (specified in the automated task creation) from the automated task run will be chosen for resubmission.

  • Failure Reason: The runs containing any of the provided Failure reasons will be resubmitted.

  • Trigger: The runs initiated by any of the selected Logic App Workflow (Standard) triggers will be resubmitted.

  • Run Action: The runs having all the selected run actions in their corresponding expected state will be chosen. If the expected status chosen is Failed and if any failure reason is provided, the run will be resubmitted only of the failure reason of the run actions matches one of the provided reasons.

Logic App workflow.gif

If no filters are chosen, all the failed Logic App Workflow runs will be resubmitted.


  • Users can now receive notifications when a Logic App (Standard) Automated Task is completed successfully.

  • The final section of the Logic App Workflow (Standard) Automated Task configuration blade includes the notification configuration section, where users can configure the desired configured Notification channels and email address(es) to receive notifications for a group or individually.

  • All the configured Notification channels will be listed in this section.

  • Multiple email addresses can also be provided so that a group of users can get notifications and stay in touch.


Was this article helpful?