From 07165a4f2ca1d10fcf08925f2fbd2e6bdd588a5a Mon Sep 17 00:00:00 2001 From: Rishi Tiwari Date: Thu, 11 Jun 2026 12:59:02 +0530 Subject: [PATCH] Update retry strategy explanation in documentation Clarified default retry strategy behavior in error handling. --- docs/sdk-reference/error-handling/retries.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/sdk-reference/error-handling/retries.md b/docs/sdk-reference/error-handling/retries.md index bcc1e04..cbdafd3 100644 --- a/docs/sdk-reference/error-handling/retries.md +++ b/docs/sdk-reference/error-handling/retries.md @@ -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