A practical field guide from Automation Ace.
Make Scenario Not Running on Schedule? Causes and Fixes
When a Make.com scenario runs fine on "Run once" but never fires on its own, the modules are working — the problem is with how the scenario is scheduled, whether it has been auto-disabled, or whether you have run into an operations or data-transfer limit. Make gives clearer signals than most tools once you know where to look. Here is how to get a scenario running reliably on its schedule.
Turn scheduling on — "Run once" is not scheduled
The most common mistake: testing with "Run once" and assuming the scenario is now live. "Run once" executes a single manual run and does nothing afterward. To run automatically, the scenario's scheduling toggle (the clock/ON switch at the bottom-left of the editor, and the ON toggle in the scenario list) must be turned on. Confirm both.
Check the schedule interval and timing
Open the scheduling settings. A scenario set to run "At regular intervals" every 15 minutes will not appear to react instantly, and one set to specific days or times only runs in those windows. If you set it to run on specific days of the month or week, make sure the current time actually falls inside a scheduled window. For custom cadence patterns, the same interval thinking applies as in running a Zap on custom schedule intervals.
Webhook triggers do not use the schedule
If your scenario starts with a webhook (instant trigger), it runs when data arrives, not on the interval. If nothing is arriving, the problem is upstream — the source is not sending to the webhook URL. Verify the webhook is receiving data before blaming the scenario. The general debugging approach is in the webhook debugging guide.
The scenario may have been auto-disabled by errors
Make disables scenarios that error repeatedly, especially unhandled errors on consecutive runs. Check the scenario's history for a run of failures and a "deactivated" notice. Fix the underlying error and add error handling so it does not happen again — Make's error-handling directives (Resume, Ignore, Rollback, Break) are covered in Make scenario error handling.
Operations and data-transfer limits
Every module execution consumes an operation, and every plan has a monthly operations quota plus a data-transfer cap. When you exhaust them, scenarios stop running until the cycle resets or you upgrade. If runs simply ceased partway through the month, check your usage dashboard before debugging logic.
Confirm with the history
The scenario history shows every scheduled run and its outcome. No history entries at all means it never triggered (scheduling or webhook problem); entries with errors mean it triggered but failed (a module problem). That single distinction tells you which half of this list to focus on. If a business-critical Make scenario keeps silently stalling, Automation Ace can make it resilient.
Disclaimer: This article may include links to apps, products, or services. Some links may be affiliate links, which means Automation Ace may earn a commission at no extra cost to you.