Retry Mechanism

Learn how Alloy Embedded's retry mechanism helps avoid failed workflow runs

Overview

As previously mentioned, Alloy Embedded handles all the rate limiting logic for Third Party App integrations. In this article, we'll take a look at how Alloy Embedded handles API retries.

Retries

When Alloy Embedded encounters a rate limit (i.e. 429 error), our system fires off a retry mechanism. By default, Alloy Embedded supports up to 40 retries. Each retry is handled with an exponential back off and jitter process to reduce the possibility of spamming the same API.

If after 40 retries the API continues to fail, Alloy Embedded exits the workflow and fails it. You can easily identify errors using our GET /workflow/errors endpoint and re-run a failed execution with our POST /workflows/rerun endpoint.

Wrapping Up

In this article, we looked at how API retries work in Alloy Embedded.