Make Scenario Deactivated? Errors and Incomplete Executions
Why Make switches a scenario off, what "not enough space to add a new incomplete execution" means, and the settings that keep a scenario running.
Make switches a scenario off when its runs keep failing, and it can no longer set failed runs aside when the store of incomplete executions is full. Both come from the same place: modules that fail with nothing to handle the failure, or a failure that keeps coming back. Fix the module that fails, clear what has piled up, and the scenario can run again.
Why Make deactivated the scenario
Every scenario has a setting for how many failed runs in a row Make accepts before it stops scheduling the scenario (Number of consecutive errors in the scenario settings). When a module without an error handler fails again and again (a login that expired, an app that changed a field, a record that no longer exists), the count is reached and the scenario is switched off. Depending on the error and on your settings this can happen sooner; Make's help pages on scenario settings and on incomplete executions describe the exact rules for your account.
What to do:
- Open the scenario's run history and find the module that failed, and why.
- Fix the cause: reconnect the login, update the mapping, or handle the missing record.
- Turn the scenario back on, and run it once while you watch.
"There is NOT ENOUGH SPACE to add a new incomplete execution"
With Allow storing of incomplete executions on, a run that fails can be kept so it can be resolved or retried later. Those stored runs take space, and when the space is used up Make cannot store another one, so the next failure is reported with this message instead of being kept.
It usually means the same failure has been happening for a while, often behind a Break error handler that keeps retrying a problem that will not pass on its own.
What to do:
- Open the scenario's Incomplete executions list and look at what is stored: most often it is one cause, many times.
- Fix that cause first, otherwise the list fills up again.
- Retry the stored runs that should still go through, and delete the ones that should not.
- Check how much storage your plan includes in Make's help pages if the list is legitimately large.
Settings to check before handing a scenario over
- Allow storing of incomplete executions is on, so a failed run is kept instead of lost.
- Every module that calls an outside service has an error handler, and Break is used for failures that pass (timeouts, rate limits) with a sensible number of retries.
- Someone receives Make's notifications when a scenario fails or is switched off, and the client knows who that is.
Importing the blueprint into VamimiAI's Make blueprint to flowchart flags modules with no error handler and scenarios that do not keep failed runs, and draws each error handler route ending in what its directive does. Make error handlers explained covers each directive, and the handover document tells the client where failed runs show up.
Questions
How do I turn a deactivated Make scenario back on?
Fix the module that kept failing first, then switch the scenario on again from the scenario list or the editor. Turning it on without a fix only lets the same failures switch it off again.
What fills up incomplete executions in Make?
Runs that failed while storing incomplete executions is on, often the same failure many times behind a Break handler. Fix the cause, then retry or delete the stored runs.
Should I turn off storing incomplete executions to stop the error?
No. Then failed runs are simply lost. Keep it on, fix the failing module, and clear the stored runs.