Skip to content

docs: correct default retry behavior for steps without a retry strategy. #202

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
yaythomas merged 1 commit into from
Jun 13, 2026
Merged

docs: correct default retry behavior for steps without a retry strategy. #202

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/sdk-reference/error-handling/retries.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,8 +11,8 @@ step body.
Retries do not consume Lambda execution time while waiting for the next retry.

When a step exhausts all retry attempts, the SDK checkpoints the final error and throws
it to your handler. If you configure no retry strategy on a step, any exception
propagates immediately without retrying.
it to your handler. If you configure no retry strategy on a step, the SDK applies a default strategy
with up to 5 retries (6 total attempts). See [Retry presets](#retry-presets).

## Configure a retry strategy

Expand Down