# How should I schedule retries for a failing workflow step?

Canonical URL: https://help.iagenify.com/faqs/workflows/how-should-i-schedule-retries-for-a-failing-workflow-step

[← Back to Workflows FAQs](https://help.iagenify.com/faqs/workflows)

HELP CENTER · FAQ Workflows 1 min read
# How should I schedule retries for a failing workflow step?
Immediate repeated retries can overload a recovering dependency and increase duplicate work. Use a bounded retry policy with a delay that grows or otherwise adapts to repeated failures, then stop and expose the failure when the operation is unlikely to recover automatically.
IaGenify
Workflows

## Classify failures first
Retry transient network interruptions, rate limits, or temporary unavailability only when the operation is safe to repeat. Do not keep retrying validation or permission errors that require a changed request or configuration.
Choose a maximum attempt count and elapsed-time budget based on the workflow’s purpose and user expectations. Add jitter when many jobs could retry together, and honor a service-provided retry-after value where applicable.
## Make exhausted work recoverable
When the limit is reached, move the item to a visible failure or review state with its attempt history and correlation identifiers. Avoid discarding the original payload or losing which side effects already completed.
Provide a controlled replay path after the cause is fixed. Preserve idempotency keys and check prior effects before retrying so recovery does not create duplicate payments, messages, or records. [← Back to Workflows FAQs](https://help.iagenify.com/faqs/workflows)