Make Scenario Not Running: Common Trigger, Scheduling and Connection Problems
When a Make scenario is not running, the source event happened but the scenario never executed. The break is between the source event and the scenario trigger. Check the scenario status, the scheduling and the connection before rebuilding the scenario, because most failures are a trigger, scheduling or connection problem.
Table of Contents
- 01.The scenario execution flow you are debugging
- 02.What to check first
- 03.Is the scenario active
- 04.Instant versus scheduled triggers
- 05.Scheduling problems
- 06.Connection and credentials
- 07.Testing the trigger
- 08.How to test it
The scenario execution flow you are debugging
A Make scenario runs when the trigger detects a source event or the schedule fires. The flow is the source event, the trigger, the scenario execution, the modules and the destination. If the scenario never runs, the trigger did not detect the event, the schedule did not fire or the scenario is inactive. The modules never get a chance to run because the scenario never started.
| Stage | What happens | Where to look |
|---|---|---|
| Scenario status | Scenario must be active | On or off, scheduling |
| Trigger type | Instant or scheduled | Webhook versus polling |
| Scheduling | Schedule must be set | Interval, active hours |
| Connection | Connection to source app | Account, credentials |
| Trigger data | Sample data must match | Test the trigger |
What to check first
- Confirm the scenario is turned on and active.
- Confirm the source event actually happened.
- Check the trigger type is instant or scheduled.
- Check the scheduling interval if the trigger is scheduled.
- Check the connection to the source application.
Is the scenario active
A scenario that is off never runs. This is the first thing to check. Scenarios can be turned off manually, by an error threshold being reached or by a plan limit. Some platforms deactivate a scenario after repeated errors. Confirm the scenario status shows active before debugging anything else. If it was deactivated, the execution history usually shows why.
Instant versus scheduled triggers
Make triggers are either instant or scheduled. An instant trigger fires the moment the source event occurs, usually through a webhook. A scheduled trigger checks for new events on an interval. If you expect an instant trigger but the scenario uses a scheduled one, the delay is normal, not a failure. Confirm which type the trigger uses, because the timing behavior differs. Scheduling frequency can depend on the Make plan.
Scheduling problems
A scheduled scenario runs on an interval you set. If the interval is too long, the scenario appears not to run when it is simply waiting for the next scheduled execution. Check the scheduling settings and the interval. Also check the active hours, because a scenario set to run only during certain hours will not run outside them. A scheduling misconfiguration looks like a trigger failure but is actually a timing setting.
Connection and credentials
The connection to the source application can break. A revoked token, a changed password or an expired session disconnects the account. The trigger cannot fire if the connection is broken. Check the connection in the scenario settings and reconnect if needed. A disconnected account often shows in the connection status or fails when you test the trigger.
Testing the trigger
Make lets you test the trigger to pull sample data. Run the test after the source event occurs. If the test returns data, the trigger works and the problem is elsewhere. If the test returns nothing, the trigger is not detecting the event. The test is the fastest way to confirm whether Make can see the event at all.
How to test it
- 1.Confirm the scenario is active.
- 2.Perform the source event in the source application.
- 3.Test the trigger to see if sample data is returned.
- 4.If no data is returned, check the connection and trigger type.
- 5.If the trigger is scheduled, check the interval and active hours.
- 6.Check the execution history for any failed or skipped runs.
Frequently Asked Questions
Why is my Make scenario not running even though the event happened?
The scenario may be off, the trigger may not match the event or the connection may be broken. Test the trigger to see if Make receives data, then check the scenario status and connection.
Why does my Make scenario have a delay before it runs?
The trigger may be scheduled rather than instant. Scheduled triggers check for new events on an interval. Confirm whether the trigger is instant or scheduled, and check the scheduling interval and active hours.
Need help applying this to your business?
PPC, Conversion Tracking, CRM and Automation Specialist. Helping businesses generate qualified leads with Google Ads, accurate tracking and automated follow-up.
Related Guides
Make Scenario Stops or Fails Mid-Workflow: How to Diagnose the Error Path
A scenario that stops halfway failed at a module, a filter or a router. Read the execution history to find the last successful module and the first failing one.
Make Webhook Receives Data but the Scenario Does Not Continue: What to Check
The payload arrived but the scenario stalled after the trigger. Check the filters, the router and the data structure to find where the bundle stopped.
Marketing Automation Workflow Not Triggering: What to Check First
A workflow that never starts usually breaks between the business event and the first action. Trace the flow from trigger to conditions to entry to find where the workflow fails to start.