← Void · A-to-Mind · Fix an automation

Make ConnectionError (502, 503, 504): when the app on the other end is down

You see: ConnectionError · 502 · 503 · 504

What it means

The app the module talks to did not answer properly: it was down, overloaded or timing out (HTTP 502, 503 or 504). Nothing is wrong with your mapping.

How to fix it

1. Check the app's status page: if it is having an outage, wait for it to recover.
2. Turn on incomplete executions in the scenario settings, so runs that hit the outage are kept and can be retried.
3. Add a Break error handler to the module so Make retries it automatically after a pause.
4. Once the app is back, replay or resolve the stored incomplete executions.

If it keeps coming back

If one app times out often, it may be the request: ask for less data per call, or split one heavy run into smaller ones.

The One-Time Fix covers one workflow. What you send and what you get back.

Sources

• Overview of error handling (Make Help Center)
• Incomplete executions (Make Help Center)
• Error handlers (Make Help Center)