Make: ConnectionError
Last verified
ConnectionErrorWhat it means
Make raises ConnectionError when the third-party app is unavailable. Make's help center associates it with HTTP 502, 503 and 504 responses, while the custom-apps developer documentation maps the wider 5xx range to it. Either way, it means Make could not get a usable answer from the app's servers.
Default behavior matches RateLimitError: scheduled scenarios without incomplete executions pause scheduling for 20 minutes; with incomplete executions enabled, Make stores the run and retries with backoff; instant scenarios rerun with backoff.
What is not wrong: your mapping and credentials. Note that authentication failures are a different error, AccountValidationError.
What it looks like
ConnectionError
[503] Service UnavailableWhy it happens
- An outage or maintenance window at the third-party app.
- The app's gateway timed out (504) on a heavy request.
- A self-hosted service called by the HTTP module is down or unreachable from Make.
- Network problems between Make and the app.
How to fix it
- Check the app's status page for an incident at the time of the error.
- Enable Store incomplete executions so runs are retried automatically after the app recovers.
- Add a Retry (formerly Break) error handler with a sensible delay and number of attempts.
- For HTTP modules calling your own server, confirm it is reachable from the internet and responds within the timeout.
- After recovery, review incomplete executions and retry any that remain.
How to stop it recurring
Keep incomplete executions enabled on any scenario that must not lose data, add error handlers on modules that call less reliable services, and monitor the services you host yourself. Subscribe to the status pages of the apps your critical scenarios depend on, so an outage alert reaches you before Make's error emails do, and avoid scheduling heavy runs during an app's announced maintenance windows.
Official documentation: help.make.com/fix-connection-errors. See all Make error messages or the Make limits and quotas.
Related errors
Definitions
- Make (formerly Integromat)Make (formerly Integromat) is a visual automation platform that connects apps and designs complex workflows us
- Error HandlingError handling is the practice of anticipating, detecting, and responding to errors in software execution, inc
- Rate LimitingRate limiting is a technique that controls the number of requests a client can make to a server within a given
- Retry LogicRetry logic is a fault-tolerance pattern that automatically re-attempts failed operations with configurable de
Quick answers
What does "ConnectionError" mean in Make?
Make raises ConnectionError when the third-party app is unavailable. Make's help center associates it with HTTP 502, 503 and 504 responses, while the custom-apps developer documentation maps the wider 5xx range to it. Either way, it means Make could not get a usable answer from the app's servers.
How do I fix "ConnectionError"?
1. Check the app's status page for an incident at the time of the error. 2. Enable Store incomplete executions so runs are retried automatically after the app recovers. 3. Add a Retry (formerly Break) error handler with a sensible delay and number of attempts. 4. For HTTP modules calling your own server, confirm it is reachable from the internet and responds within the timeout. 5. After recovery, review incomplete executions and retry any that remain.
Error handling you can see in the workflow
Autonoly workflows have per-node retries, timeouts, continue-on-fail and error-handler branches, so a failing step can be retried or routed instead of stopping the whole run. Saved workflows have no loop node; lists are worked through by the AI agent or one run per trigger item.
Also see Visual workflow builder.