Make · App modules
ConnectionError
ConnectionError in Make means the third-party app is unavailable, for example offline for maintenance. Check the app status page, add the Retry error handler to the module, and enable incomplete executions.
VerifiedLast verified
01Error text
ConnectionError02Likely causes
- The app is unavailable, for example because it is offline for maintenance.
- Make uses HTTP status codes 503 and 504 to identify this error.
03How to fix it
- Check the status page of the app.
- If the scenario starts with an instant trigger such as a custom webhook, consider enabling Process data in order in the scenario settings.
- Add the Retry error handler to the module that causes the errors, and set the delay and number of attempts to suit the scenario.
- Enable incomplete executions in the scenario settings.
iNotes
With no error handler, a scheduled scenario with incomplete executions disabled is paused for 20 minutes and not rerun. With incomplete executions enabled, Make retries the run with exponential backoff.
04Official documentation
→Related errors
- AccountValidationErrorAccountValidationError in Make means Make cannot authenticate in the third-party app, for example after credentials change or expire without an update in the connection. Review your credentials in the app and the connection in Make, and create a new connection if necessary.
- RateLimitErrorRateLimitError in Make means requests to an app exceeded its API rate limit, which corresponds to HTTP 429 Too Many Requests. Lower the request rate with the scenario rate limit, longer schedule intervals, bulk or aggregator modules, or a Sleep module before the failing module.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Make work:Open Make jobsMake rates and salaries