If a scenario is deactivated, it won’t reactivate automatically, unless you build another automation that reactivates it using the Make API (here).
However, it also depends on the scenario type
- Is it a webhook scenario?
- Is it a scheduled scenario?
And the error type
- Is it an issue with a connection?
- Was it a rate limit on an API?
- Is it an error on the data?
It’s possible that when you re-activate the scenario, it fails again.
For example, if it’s a webhook scenario, and you kept the default settings, the message is back to the webhook queue, so, when you restart the scenario, it picks the same message again; which is great if you don’t want to loose any data, but if it’s the actual data that makes the scenario fail, it will fail again…
The best approach is to use Error Handlers, and Incomplete Executions, since they allow you to handle most errors, and avoid your scenario from deactivating. It’s not a simple topic, but once mastered, you could have way more stable scenarios.
Please have a look at the academy trainings here