Overview
Automated tasks in Business Applications fail for a small set of well-understood reasons: usually a permissions gap on the service principal, an invalid schedule, or a resource state that doesn't support the requested operation. This article identifies the most common causes and how to fix them. Automated tasks are scheduled or manually triggered operations that run against Azure resources, such as starting or stopping a Logic App, sending a message to a Service Bus queue, or triggering a Data Factory pipeline.
Business value
Automated tasks reduce manual intervention in routine resource operations and support incident response workflows. Resolving task failures quickly restores automated operations and prevents operational gaps that would otherwise require manual remediation.
How it works
An automated task executes a defined action against an Azure resource on a schedule or on demand. Turbo360 invokes the action through the service principal, which must have sufficient permissions on the target resource. The task result (success or failure) is recorded in the task history for the resource.
Task failures typically occur because the service principal lacks the required permission, the target resource is unavailable, the task configuration has an error, or the execution schedule conflicts with a resource state.
Troubleshooting
-
Automated task fails with an authorization error
Cause: The service principal does not have the required permission on the target resource. Most operations require at least Contributor access at the resource or resource group scope.
Fix: In the Azure portal, assign the appropriate role to the Turbo360 service principal on the target resource. For resource-specific permission requirements, refer to the task configuration article for the relevant resource type. Retry the task after the role assignment propagates. -
Scheduled task does not run at the configured time
Cause: The task schedule is disabled, the recurrence expression is incorrect, or the task was saved without a valid schedule.
Fix: Navigate to the resource in the Business Application tree view, open the Automated tasks section, and verify the schedule is enabled and the recurrence is correctly configured. Save any changes and confirm the next scheduled run time is shown. -
Task runs but the target resource does not change state
Cause: The resource is in a state that does not support the operation (e.g. attempting to start a Logic App that is already running, or triggering a pipeline that is already in progress).
Fix: Check the current state of the resource in the resource dashboard or directly in the Azure portal. Ensure the task action is valid for the current resource state. Review the task history for the specific error message returned by the Azure API. -
Inline automated task is not visible for a resource
Cause: The resource type does not support the requested operation, or the user does not have the permission required to view or run inline tasks for that resource.
Fix: Confirm that the resource type supports inline automated tasks by checking the relevant resource article under Resources. Verify that the user has the appropriate Business Applications permission level. Inline automated tasks surface on the resource view and do not require a separate tasks permission; only the resource-level permission applies. -
Task history shows no record of a recent task execution
Cause: The task was triggered but did not execute because the Business Application was in a paused or inactive state, or the task was removed before it ran.
Fix: Confirm the Business Application is active and the automated task is still configured. Check the Task history for the resource to see whether any execution was attempted. If no record exists, re-trigger the task manually and monitor the history for the result.