Retry policies

Webhooks

Webhooks expect an HTTP 2xx response to be considered delivered. By default, we will attempt delivery 5 times before marking a webhook as failed using an exponential back-off algorithm.

Failed webhooks can still be collected from the /webhook/poll endpoint.

Webhooks adhere to an at-least-once delivery policy. This means that we will potentially retry even if your app acknowledges receipt (e.g, if network conditions prevent the request completing, for example).

Tasks

Workflow Task Runs will be retried if they do not return a valid success or error response. While this is handled for you with native tasks, if deploying serverless functions within your own account or using embedded JS tasks, you must always return appropriately to avoid retries.

Should we see a retry level >30%, we will disable your Task Runs and this will render all related Workflow Runs inoperable also.