Marketing Cloud Engagement | Why Automation Studio Skips Scheduled Runs and How to Fix It

Causes of Skips and How to Fix Them

1. Processing Time Overruns

a. Chronic Processing Overruns

When a single automation run takes longer than the schedule interval (for example, every 15 minutes or every hour), the system automatically skips the next scheduled run to prevent overlapping executions. For example, if an automation scheduled to run every 24 hours takes 36 hours to complete, the next run is skipped.

Q. How do I prevent skips caused by chronic overruns?

Consider the following approaches:

Set the schedule interval significantly longer than the actual processing time (for example, change a 15-minute interval to 45 minutes or 1 hour).
Avoid placing multiple heavy activities in a single step — split the processing across multiple steps or separate automations.

Important: The longer you operate Marketing Cloud Engagement, the more data it tends to accumulate. Activities that initially completed quickly may gradually — or suddenly — take much longer or time out. To minimize this risk, optimize your queries and design automations to process and update only the data you need.

b. Wait Activity Design Issues

When an automation contains a Wait activity and the next scheduled time arrives while the automation is waiting, the next run is skipped.

Q. Why does having a Wait activity cause skips?

For example, if an automation scheduled to run every hour contains a 2-hour Wait activity, the next scheduled time always arrives while it is waiting, causing a skip. Set the schedule interval longer than the total execution time including the Wait activity's wait time, or shorten the Wait activity's duration.

c. Temporary Overruns Due to Resource Contention

Because Marketing Cloud is a multi-tenant environment, processing can concentrate at specific times across the platform, or database maintenance and updates can cause temporary performance degradation and processing queue delays. As a result, processing time may extend into the next schedule slot, or delays in the scheduler's own assignment process may cause skips.

Q. Are there ways to reduce skips caused by resource contention?

The following approaches are effective:

Avoid peak times such as the top or bottom of the hour, use the "Use Suggested Time" feature, and set offset times like "8:07" or "8:12" (reference: Schedule an Automation).
If the skip is a one-time occurrence due to maintenance and immediate recovery is needed, perform a manual recovery using [Run Once] after the environment stabilizes.

2. File Drop Queue Settings

In automations triggered by a file upload, if queue settings are disabled and a new file with the same name is dropped while the automation is running, the new trigger request is ignored and a skip occurs.

Q. How do I prevent skips with a File Drop trigger?

Consider the following approaches:

Enable the queue in the automation settings to ensure processing always runs.
Make dropped file names unique using timestamps or similar methods, and change your operational flow to upload the next file only after the previous run completes.

Preventive Measure: Configure Notifications

To detect skips and errors quickly, register an email address under [Notification Settings] in the [Activity] tab of the automation for the item "Runtime Error or Skipped Run" This allows you to receive automatic alerts when a skip occurs.

Reference: Get Automation Studio Notifications

General Information

Required Cookies

Functional Cookies

Advertising Cookies