Make.com Scenario Monitoring: Catch Errors and Scenarios That Stop Running
By Muhammad Usman · · 6 min read
What Make does for you
Make has useful built-in tools:
- Error handlers (Resume, Ignore, Break, Commit, Rollback) on individual modules
- Incomplete executions, which store failed runs so you can retry them
- Email notifications about errors and deactivated scenarios
Set these up first. They are the foundation.
What Make doesn't tell you clearly
- A scenario that stops running. If a webhook stops receiving data or a schedule is changed, nothing fails, so nothing alerts.
- A scenario that is switched off. Make can deactivate a scenario after repeated errors. The email is easy to miss, and the automation is simply off until someone notices.
- Silent failures. A run "succeeds" but processes zero bundles because a filter or a changed API field drops everything.
- Slow degradation. More and more runs fail, but never enough to feel like an outage.
A monitoring setup that works
- Turn on error notifications in your Make profile and send them to an address you actually read.
- Add error handlers to modules that call external APIs, and route errors to a Slack or email module.
- Track operations per run. A scenario that normally processes 50 bundles and suddenly processes 0 needs a look.
- Add a heartbeat. Alert when an important scenario hasn't run for longer than its normal schedule.
- Watch the error rate per scenario over the last 24 hours.
- Send a weekly summary of success rates to whoever owns the automations.
Using the Make API
Make's API lets you read scenario status and execution logs with a token (Profile → API access, with the scenarios:read scope). A monitoring tool can poll it regularly, calculate error rates and detect scenarios that stopped, without changing your scenarios at all.
How ProofMyAI monitors Make
ProofMyAI connects to Make with a read-only API token and your scenario IDs, checks their logs every 15 minutes and alerts you about failures, silent failures, error spikes and scenarios that stopped running, by Slack, email, Teams, Telegram or WhatsApp. See the setup steps.
✅ Key takeaways
- Use Make's error handlers, incomplete executions and notifications first.
- Make won't clearly warn you about scenarios that stop running or process nothing.
- Add heartbeat, zero-output and error-rate checks for important scenarios.
- A read-only API token is enough for outside monitoring.
❓ Frequently asked questions
Why did my Make scenario turn off?
Make can deactivate a scenario after repeated consecutive errors. Check the scenario's history for the errors, fix the cause, and switch it back on. A heartbeat alert tells you when this happens.
Can I get Make error alerts in Slack?
Yes. Add an error handler route with a Slack module, or use a monitoring tool that reads the Make API and sends alerts to Slack, Teams, email or WhatsApp.
Does monitoring change my scenarios?
No. Monitoring through the Make API only reads scenario logs with a read-only token.