--- title: "Configuring Data Factory Pipeline automated tasks" slug: "configuring-data-factory-pipeline-automated-tasks" updated: 2026-09-07T18:32:16Z published: 2026-09-07T18:32:16Z canonical: "docs.turbo360.com/configuring-data-factory-pipeline-automated-tasks" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.turbo360.com/llms.txt > Use this file to discover all available pages before exploring further. # Configuring Data Factory Pipeline automated tasks ## Overview Data Factory Pipeline automated tasks let you rerun failed Azure Data Factory pipeline runs on a schedule. When a pipeline run fails, the task detects the failure and automatically triggers a rerun, reducing the need for manual intervention and restoring pipeline continuity faster. ### Business value Failed Data Factory pipeline runs left unaddressed can delay downstream processes and require manual monitoring. Data Factory Pipeline automated tasks automate the detection and rerun of failed pipeline runs, helping you restore execution continuity without manual intervention. ## How it works Data Factory Pipeline automated tasks work by scanning for pipeline runs that failed within a configurable lookback window (for example, the past 12 hours). When the automated task runs on its schedule, it identifies eligible failures based on the filters you configure, then triggers reruns for those runs. The task supports the following configuration options: - **Failure Occurrence:** defines the lookback window in hours. Only pipeline runs that failed within this window are selected for rerun. - **Include the previous reruns:** when enabled, the task also considers runs that were already rerun once but are still in a failed state. - **Rerun the ignored runs of previous run:** when enabled, the task includes pipeline runs that were skipped or ignored during a previous rerun attempt. - **Run task once immediately after saving:** when enabled, the task executes once immediately after you save the configuration, in addition to running on its configured schedule. ## Steps Use the following steps to configure a Data Factory Pipeline automated task. Navigate to **Business Applications** > **Automated tasks** > **New configuration** to get started. ### Configure the rerun filters Configuring the rerun filters determines which failed pipeline runs the task targets when it executes. 1. Select **Data Factory Pipeline** from the **New configuration** dropdown. 2. Set the **Failure Occurrence** value to the number of hours defining your lookback window. 3. Enable any of the following options as required: - **Include the previous reruns** - **Rerun the ignored runs of previous run** - **Run task once immediately after saving** 4. Click **Next**. ### Schedule the task Scheduling controls when the automated task runs and whether it repeats. 1. Configure the recurrence schedule for the task. 2. Enable the task to activate it. 3. Click **Next**. ### Alert configuration Notification settings control which channels and recipients receive alerts when the task completes or fails. 1. Select the notification channels you want to use. 2. Enter one or more email addresses to receive notifications. 3. Under **Advanced settings**, enable either or both of the following options as required: - **Send alerts only when the automated task fails:** notifications are sent only when the task itself fails to execute. - **Send alerts only when the completed count is greater than 0:** notifications are sent only when at least one pipeline run was successfully rerun. 4. Click **Save**. Note: When both Advanced settings options are enabled, you receive a notification if the task fails **or** if at least one run was successfully rerun. ## Troubleshooting 1. **No pipeline runs are rerun after the task executes** Cause: The Failure Occurrence lookback window is set too short, or no pipeline runs failed within the configured timeframe. Fix: Increase the Failure Occurrence value and verify that failed runs exist within the extended window in the Azure Data Factory monitoring view. 2. **The task runs but notifications are not received** Cause: No notification channels are configured, or the Advanced settings filters exclude the current task result. Fix: Confirm at least one notification channel is selected. If Advanced settings are enabled, verify that the task outcome matches the configured filter conditions. 3. **Previously rerun failures are not being picked up** Cause: The **Include the previous reruns** option is not enabled. Fix: Edit the task configuration and enable **Include the previous reruns** under the rerun filters. 4. **The task does not run immediately after saving** Cause: The **Run task once immediately after saving** option was not enabled during configuration. Fix: Edit the task and enable **Run task once immediately after saving**. The immediate execution only occurs at save time and cannot be triggered retroactively. 5. **Ignored runs from a previous rerun are not being included** Cause: The **Rerun the ignored runs of previous run** option is not enabled. Fix: Edit the task configuration and enable **Rerun the ignored runs of previous run**. ## FAQs 1. **Can I target a specific pipeline within a Data Factory, or does the task apply to all pipelines?** The task applies to all pipelines within the selected Azure Data Factory resource. The Failure Occurrence window and other filter options control which failed runs are eligible, but there is no per-pipeline scoping available. 2. **What are "ignored runs" in the context of the Rerun the ignored runs of previous run option?** Ignored runs are pipeline runs that were skipped or bypassed during a previous automated rerun. This happens when a run was in a state the task could not process at that time. Enabling this option ensures those runs are picked up on the next execution. 3. **If I enable Run task once immediately after saving, will it run again on the next scheduled interval?** Yes. The immediate execution is a one-time action triggered at save time only. The task continues to run on its normal configured schedule after that, independently of the immediate run. ## Related articles - [What is an automated task?](https://docs.turbo360.com/docs/what-is-automated-task) - [Scheduling an automated task](https://docs.turbo360.com/docs/scheduling-an-automated-task) - [Task history](https://docs.turbo360.com/docs/task-history) - [Configuring Synapse Pipeline automated tasks](https://docs.turbo360.com/docs/configuring-synapse-pipeline-automated-tasks) - [Configuring Management operations tasks](https://docs.turbo360.com/docs/configuring-management-operations-tasks)