Skip to main content

Understanding Retry Logic in API Exports

Daniel Wiener avatar
Written by Daniel Wiener
Updated over 2 weeks ago

When exporting data via Autobound’s API Export feature, some requests may fail due to temporary issues such as rate limits, timeouts, or brief network interruptions.

The Retry on Failure setting ensures that these transient errors are handled automatically without manual intervention.


How It Works

Failed rows in any action or export column are automatically retried when this setting is toggled on.

Exponential Backoff with Jitter:

  • Retries happen using an increasing delay pattern — for example:

  • 2 seconds → 5 seconds → 10 seconds → 20 seconds

  • Each delay includes a random “jitter” of 0–2 seconds to prevent multiple requests from repeating simultaneously.

Retry Limits:

  • Autobound makes a limited number of attempts (typically 3–10, depending on error type).

  • If all attempts fail, the row remains in an error state so you can review or re-run it manually later.

Scope:

  • This logic applies consistently across all exports and integrations, ensuring reliable delivery even when external APIs throttle or experience downtime.


Best Practices

  • Enable Retry on Failure when exporting to platforms that frequently rate-limit or enforce API quotas.

  • Leave it off for simple, lightweight exports that complete instantly.

  • Review retry results in the campaign’s Prospects tab—hover over the cell to see error messages or timestamps for each attempt.

Did this answer your question?