Overview
This article answers common questions about automated tasks in Business Applications, including task types, scheduling, execution history, and troubleshooting failed runs.
Business value
Automated tasks eliminate manual operational overhead by triggering actions on Azure resources directly from Turbo360. Getting answers to common configuration and execution questions helps teams deploy reliable automation faster.
How it works
This FAQ covers three areas: understanding task types and scope, configuring schedules and triggers, and investigating task failures. Each answer references the relevant documentation for fuller procedural guidance.
FAQs
-
What is an automated task in Business Applications?
An automated task is an action executed on an Azure resource (such as starting a Logic App, purging a Service Bus queue, or triggering a Data Factory pipeline) either on a schedule or in response to a monitoring alert. Tasks run within the context of a Business Application. See What is an automated task? for a full overview. -
Which Azure resource types support automated tasks?
Automated tasks are available for Service Bus (queues and topics), Event Grid, Event Grid Domains, Event Hub, Logic Apps (Consumption and Standard), Storage Accounts, Data Factory Pipelines, Synapse Pipelines, Runbooks, Power Automate flows, and Databricks. See the Task configurations category for the setup article for each resource type. -
Can I trigger an automated task from a monitoring alert?
Yes. Each monitoring rule has an Actions column where you can assign a task to trigger when that rule's condition is met. From the resource's Monitoring tab, open the Rules sub-tab, locate the rule, and select the automated task from the Actions dropdown. The task fires automatically when the rule breaches its threshold. See Inline automated tasks for the full configuration steps. -
What is the difference between a scheduled task and an inline automated task?
A scheduled task runs on a recurring schedule you define (for example, every day at midnight). An inline automated task runs automatically when a linked monitoring rule fires an alert. You can use both types on the same resource. -
Where can I see the execution history of an automated task?
Open the Business Application, navigate to the resource, and select the Automated tasks section. The Task history view shows run timestamps, execution status, and error messages for each task run. See Task history. -
Why did my automated task fail to execute?
The most common causes are: the service principal does not have sufficient permissions on the target resource (Contributor is required for most write operations); the target resource was unavailable or in a failed state when the task ran; or a configuration error in the task definition (for example, an invalid queue name). Review the error details in Task history and verify the service principal permissions for the resource type. -
Can I run the same automated task across multiple resources at once?
Yes, using bulk operations. From the Business Application resource list, select multiple resources of the same type and trigger the task from the Actions menu.