Automatic retry of incomplete executions

Make checks the origin of every incomplete execution when it's created. Make automatically retries incomplete executions that have been created because of:

and incomplete executions that were created with the Retry error handler with the automatic run completion enabled.

Make takes the following steps when Make retries incomplete executions:

Make schedules automatic retries with the Exponential backoff schedule. The backoff schedule prevents the situation when you would get the same error multiple times in a row.

For example, when you get the ConnectionError because the app is unavailable, it might take some time until it's back. Make spaces out the retry attempts to get a successful retry even at a later time after the original error.

Other error type usually require changes in the incomplete execution and manual resolving. Make doesn't retry these error types automatically by default.

After Make schedules the retries, Make runs the scenario again, starting with the module that caused the error.

For each scenario, there is a limit of 3 incomplete execution retries running in parallel. If there are more incomplete executions scheduled from the same scenario, Make retries them in batches of 3 after the previous batch finishes.

In addition, the retry doesn't start when the original scenario is running already.

The 3 parallel retries limit applies to retries from the same scenario. When Make retries incomplete executions from multiple scenarios, then each of them has their own limit.

For example:

You have a scenario that runs for 10 minutes every hour. There was a disruption of a third party service for 5 hours.

If a retry attempt succeeds, Make marks the incomplete execution as Resolved and stops retrying.

If all of the retry attempts fail, Make marks the incomplete execution as Unresolved. You can then retry the incomplete execution when the app that caused the error is available again or you can resolve the incomplete execution manually.