Configuring Logic App automated tasks

Overview

Logic App automated tasks let you configure scheduled jobs that automatically resubmit failed Logic App (Consumption) runs. Instead of monitoring runs manually and resubmitting failures one by one, you define filter conditions and a schedule — Turbo360 handles the rest.

Business value

Failed Logic App runs left unaddressed can silently break downstream business processes. Automated tasks eliminate manual resubmission, reduce incident response time, and ensure critical integration workflows recover consistently without operator intervention.

How it works

When an automated task runs, Turbo360 queries the Logic App for failed runs within the configured time window and applies your filter conditions to select which runs to resubmit. Only runs that match all specified filters are resubmitted. If no filters are configured, all failed runs within the time window are resubmitted.

Turbo360 then triggers a resubmit action for each selected run and records the outcome in the task history. You can review results, completed counts, and any errors from the task history view.

Steps

Use the following steps to create and configure a Logic App automated task. Navigate to Business Applications > Automated tasks to get started.

Create a Logic App automated task

Creating an automated task schedules Turbo360 to automatically resubmit failed Logic App (Consumption) runs based on the filters and schedule you define.

1. Click New configuration.
2. Select Logic App as the resource type.
3. Select the target Logic App from your Business Application.
4. Configure the schedule for the task.
5. Under Resubmit filters, configure one or more of the following:
   • Failure Occurrence — resubmit runs that failed within the past x hours from the task run time. Set x to match your acceptable failure window.
   • Failure Reason — resubmit only runs whose failure reason matches one of the values you specify.
   • Trigger — resubmit only runs that were initiated by one of the selected Logic App triggers.
   • Run Action — resubmit only runs where the specified run actions are in the expected state. If you also set a Failure Reason, the run action's failure reason must match one of the provided reasons.
6. Under Notifications, configure your notification channels and recipients (see Alert configuration).
7. Click Save.

Alert configuration

Configure notifications in the final section of the automated task configuration panel. You can set one or more notification channels and provide individual email addresses or a group distribution list.

Under Advanced settings, you can restrict when notifications are sent:

• Send alerts only when the automated task fails — you receive a notification only if the task itself fails to execute.
• Send alerts only when the completed count is greater than 0 — you receive a notification only when at least one run was resubmitted.

Enabling both options notifies you when the task fails or when the completed resubmission count exceeds zero.

Example scenario

Your order-processing Logic App (Consumption) occasionally fails due to a transient downstream API timeout. Rather than checking for failures each morning, you configure an automated task to run every hour. You set Failure Occurrence to 1 hour and Failure Reason to ActionFailed. Each hour, Turbo360 identifies any runs that failed with that reason in the past hour and resubmits them automatically. You enable Send alerts only when the completed count is greater than 0 so that you only receive an email when a resubmission actually occurs.

Troubleshooting

1. Automated task runs but no runs are resubmitted
   Cause: The filter conditions are too restrictive, or no Logic App runs failed within the configured time window.
   Fix: Review the Failure Occurrence window and confirm that failed runs exist in the Logic App run history within that period. Broaden or remove filters to verify.

2. Task fails with an authorization error
   Cause: The service principal used by Turbo360 does not have sufficient permissions on the Logic App.
   Fix: Verify that the service principal has the Logic App Contributor role (or equivalent) on the target Logic App resource in Azure.

3. Resubmitted runs fail again immediately
   Cause: The underlying cause of the original failure has not been resolved (for example, a downstream service is still unavailable).
   Fix: Investigate the failure reason in the Logic App run history. Address the root cause before relying on automated resubmission.

4. Notifications are not being received
   Cause: Notification channels are not configured, or the Advanced settings filters are preventing delivery.
   Fix: Confirm that at least one notification channel and recipient is configured. If Send alerts only when the completed count is greater than 0 is enabled, verify that resubmissions are actually occurring.

5. Task history shows no records
   Cause: The task has not yet run, or runs are being filtered before reaching the resubmit stage.
   Fix: Check the task schedule and confirm it is active. Review the task's last run time in the Automated Tasks list.

Related articles

• What is an automated task?
• Logic App Workflow (Standard) automated tasks
• Storage Account automated tasks
• Task history