Make

Make scenario deactivated by itself: causes and how to be warned

Make deactivates a scenario after repeated errors. Why, how to avoid it, and how to know that a scenario has stopped running.

By Abdellah El Kharraze · · 2 min read

Key takeaways
  • Make deactivates a scenario after several consecutive errors to protect your operations.
  • A deactivated scenario sends no further alerts.
  • An error handler prevents many deactivations.
  • Check scenario status from the outside, daily or continuously.

You open Make and a scenario that had been running for months is inactive. Nobody touched it. Make deactivated it, and it had a good reason to.

Why Make deactivates a scenario

When a scenario fails several times in a row, Make deactivates it so it does not burn your operations in a loop. Some errors lead to faster deactivation, for example a connection that has become invalid. Make sends an email when this happens.

The real problem: the silence that follows

A deactivated scenario no longer runs, so it no longer errors, so it no longer sends anything. If the deactivation email landed on a Friday evening in the inbox of a colleague on leave, the scenario can stay stopped for weeks.

Reducing deactivations

  • Add an error handler on fragile modules: resume with a default value or ignore the faulty item rather than stopping the scenario.
  • Enable storage of incomplete executions so you can replay them.
  • Keep an eye on expiring connections to third-party services.
  • Send notifications to a shared address, not to one person.

Being warned for certain

The only reliable check happens from the outside: query the Make API regularly and compare each scenario's status with what it should be. A monitored scenario that is inactive is an incident, whatever the cause. Nokto opens that incident within two minutes and keeps it open until reactivation. The guide Monitoring your Make scenarios covers the rest.

Frequently asked questions

Does Make reactivate a scenario by itself?

No. Once deactivated, the scenario waits for manual reactivation.

AE
Abdellah El Kharraze

Founder of Nokto and Owepo, based in Nice, France. Network and security engineer for large enterprises until 2016, then ten years building n8n and Make automations for small businesses.

Your first monitored workflow in ten minutes.

Connect an n8n instance or a Make team: Nokto discovers your workflows, learns their rhythm and warns you at the first anomaly.

14 days free · no credit card · cancel anytime