Automation Answers

Why Is My Make Scenario Not Running on Schedule?

Troubleshoot a Make scenario that misses scheduled runs by checking activation, schedule settings, timezone, queues, and execution history.

By Automation Ace Editorial TeamReviewed for technical accuracy by Troy TessalonePublished Updated

Short answer

Why Is My Make Scenario Not Running on Schedule?

A Make scenario commonly misses its schedule because scheduling is off, the interval or timezone is not what you expect, a previous execution is still running, or the trigger returns no new bundles. Turn scheduling on, open the schedule settings to verify interval and timezone, inspect execution history at the expected time, and run once with a new qualifying source item.

Common causes

  • The scenario is saved but scheduling is toggled off.
  • The selected schedule, start date, or account timezone differs from the assumed local time.
  • A prior execution is still active or queued, blocking the next run.
  • The trigger runs successfully but returns zero new bundles.
  • The connection, data store, or module configuration changed after activation.

Diagnostic steps

  1. Confirm the scheduling toggle is on, not merely that the scenario was saved.
  2. Open schedule settings and verify interval, days, start time, and timezone.
  3. Inspect scenario history at the expected timestamp, including successful runs with zero operations.
  4. Create a new qualifying source item and use Run once while watching the trigger module.
  5. Review incomplete executions, rate-limit errors, and any long-running prior execution.
  6. Reauthorize the connection only after recording the current settings and error details.

Example

A scenario expected at 9:00 a.m. New York time runs at 1:00 p.m. because its organization timezone is UTC. Setting the intended timezone and confirming the displayed next-run timestamp fixes the apparent missed schedule.

Caveats

A scheduled execution with zero bundles is different from a schedule that never started. Daylight-saving transitions and “every day” versus “specific days” settings can shift expectations. Avoid repeatedly using Run once against live actions unless those actions are safe to repeat.