Is the scenario switched on?
Run once never switches a scenario on. Only the switch does.
In the lesson, the last steps are: click the Save icon in the toolbar, then click the switch next to Daily at 5:00 PM. In the first scenario lesson it is Activate scenario. If the switch is off, nothing runs on its own.
Is the schedule what you think it is?
Open the schedule by clicking the clock label in the toolbar and read it.
| Setting | What to check |
|---|---|
| Run scenario | At regular intervals, Daily, Days of the week, Days of the month, or On demand |
| Time 1 | 17:00 means 5 PM, in 24-hour time |
| Time zone | Shown under the field; it comes from your Make profile or organization |
| Interval | Every 15 minutes is a common default; your plan may set a minimum |
On demand means it only runs when you click Run once or call it from another scenario. A daily summary set to 17:00 in a time zone three hours away arrives at 2 PM or 8 PM your time.
Is the trigger finding anything new?
A scheduled scenario that starts with a "Watch" module, like Google Forms Watch Responses, runs on time but does nothing when there's nothing new.
The first time you set it up, Make asks where to start. In the lesson you pick All, so the test can use existing responses. After that, it only picks up responses newer than the last one it processed. Look at the run history: runs with zero bundles mean the scenario is running fine and simply had nothing to do.
Did it run but stop partway?
Open History. A run with a red module stopped at that module. If it failed several times in a row, Make may have switched the scenario off. Make Scenario Errors covers the common messages.
Are you out of operations?
Every module that runs uses operations, and when your plan's monthly operations run out, scenarios stop until the quota resets or you upgrade. Check the usage on your organization's dashboard. A scenario every 15 minutes uses operations even when it finds nothing, because the trigger itself counts.
Try it free, step by step
On a Schedule: A Daily Summary Email from a Google Sheet in Make.com. Build a Make scenario that runs every day at 5 PM, finds today's rows in Google Sheets, combines them with a Text aggregator and emails one summary with Gmail. You do every step yourself in a practice copy of Make, it checks your work as you go, and “Do it for me” finishes any step you get stuck on. Free, and nothing touches your real accounts.
Start the free lessonA quick checklist
- Switch is on.
- Schedule type is not On demand.
- Time and time zone are right.
- The trigger has new data to pick up.
- History shows no red modules.
- Operations are left on the plan.
- The scenario was saved after the last change.
Key takeaways
- Run once is a test; the scenario switch is what makes it run by itself.
- Check the time zone under the schedule's time field.
- Zero-bundle runs mean the trigger found nothing new, not that the scenario is broken.
- Running out of operations stops every scenario until the quota resets.
Frequently asked questions
- Why does my Make scenario only run when I click Run once?
It is switched off or scheduled as On demand. Turn on the switch and pick a schedule such as Daily or At regular intervals.
- Where do I set the time zone for a Make scenario?
The time zone shown under the schedule comes from your Make profile and organization settings. Change it there if it's wrong.
- Does a scheduled scenario use operations when there is nothing new?
Yes. The trigger module runs and counts on every scheduled check, even if it finds no new data.
- What is the n8n version of this problem?
In n8n a workflow has to be published to run on its schedule; n8n Workflow Not Running covers it. Make and Zapier are both in the free Make & Zapier Jump Start course.
