TheResume
option is the ability to perform a retry on an operation that has encountered an error. When using Make.com, this is useful when a module encounters a transient error and the problem is likely to be resolved automatically. resume allows you to recover from the error and keep your workflow moving forward.

What does Resume do?
- retriesthe module (action) that encountered an error based on specified conditions.
- this is especially useful for recoverable errors, such as network delays, exceeding API limits, and temporary failures.
- executes based on the set number of retries and retry interval.
When to use Resume
- when there is a possibility of resolving a transient issue
- Response delay or throttling issues when making API calls.
- external server connection failures.
- temporary network errors.
- when retrying is likely to recover from the error
- for example, when an external API temporarily fails to return data, but is likely to succeed after a few seconds.
- when automating long-running tasks
- when trying to handle intermittent errors in a large data synchronization operation.
To set upResume
1. add an error handler

- On the Edit Make.com scenario screen, hover over Modules.
- click theAdd error handler button.
- under Error handler, select the
Resume
option.
2. set retry conditions
When setting up theResume
option, you can adjust the following conditions
- number of retries (Retries)
- set how many times to retry when an error occurs.
- example: 3 times.
- retry interval (Interval)
- set the retry interval in seconds.
- example: Retry every 5 seconds.
3. add retry conditions (Optional)
- you can set whether to retry based on specific error codes or messages
- example: Retry only on
HTTP 503
errors.
- example: Retry only on
Examples of using Resume
example 1: External API calls
- scenario: Sending data to an external API.
- problem:
HTTP 503 (Service Unavailable
) error due to network connectivity issues. - solution
- Using
Resume
, set up 3 retries at 5 second intervals. - if successful on the 3rd attempt, the workflow continues as normal.
- Using
example 2: Sending emails
- scenario: Sending an email through an SMTP server.
- problem: The server is temporarily busy or unresponsive.
- solution
- Use
Resume
to retry twice, 10 seconds apart. - if retries fail, log an error or move on to the next action.
- Use
Cautions for using Resume
- set retry limits
- too many retries can waste time and resources, so set an appropriate number and interval.
- determine if recovery is possible
- make sure the error is temporary. a configuration issue on the server or an invalid request might not be resolved by retrying.
- add logging
- set up logging when errors occur so that you can analyze the cause if the problem recurs.
Resume summary
item | description |
---|---|
role | retries the module in case of an error and attempts to recover. |
use cases | network errors, API response delays, temporary failover. |
configuration elements | number of retries, retry interval, run only under certain conditions. |
cautions | use it only for tasks that are likely to be resolved by retrying, and set conditions and limits to prevent it from repeating indefinitely. |
When used effectively, the Resume feature can increase the reliability and automation of your workflows