An external payment API in an order workflow fails temporarily.
Retry with exponential backoff and then continue to a compensation step after a limit.
Which design is most appropriate?
Define Step Functions Retry and Catch behavior on the relevant states so transient failures and compensation are explicit.
Detailed explanation
Restarting all steps can duplicate completed work and cause unintended side effects.
Restarting all steps can duplicate completed work and cause unintended side effects.
Step Functions can define retry conditions and failure transitions for individual states.
Step Functions can define retry conditions and failure transitions for individual states.
DNS cache lifetime does not control application retry behavior.
DNS cache lifetime does not control application retry behavior.
S3 Lifecycle manages object transitions and expiration, not workflow retries.
S3 Lifecycle manages object transitions and expiration, not workflow retries.
Check official documentation
Compare the following points with the official documentation.
AWS Step Functions Retry/Catchの公式説明を確認する。
What to confirm
ワークフローの失敗処理を再試行と分岐として表現できる。
Key points
- Step Functions
- Retry
- Catch
Notes
- Environment: AWS公式Step Functionsドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Failure scope
State-level retry avoids replaying completed work across the entire workflow.
Compensation
A compensating action reverses or offsets a side effect when the business operation cannot continue.