Home › Guides › How do I handle errors when APIs go down or respond slowly?

How do I handle errors when APIs go down or respond slowly?

By the Astraq editorial team · independent guide
October 13, 2026
How do I handle errors when APIs go down or respond slowly?

Add retry logic

Most platforms have built-in retry options. Set retries to 2–3 attempts with delays between each (5–30 seconds). This handles temporary hiccups without manual intervention.

Set reasonable timeouts

If an API doesn't respond within 30 seconds, tell it to fail fast instead of hanging. Check your platform's timeout settings and adjust per the API's typical response speed.

Use error handlers

Create a separate path in your workflow for when steps fail. Common approaches: send yourself a notification, log the error to a spreadsheet, or queue the request for manual retry. Don't let failed runs disappear silently.

Add status checks

Before running critical workflows, use a status-check step that pings the API first. Skip the workflow if the service is down rather than failing partway through.

Monitor and alert

Enable notifications when workflows fail repeatedly. This signals a real problem (API change, service outage, or your credentials broke) that needs attention.

Keep backups

For critical automations, log all data processed to a backup system (Google Sheets, database). If something fails, you have a record to retry from.

Reader reviews

Write a review

← All guides