From f9cdb58a98d25a978ae37c5f7e8dc3926a07892e Mon Sep 17 00:00:00 2001 From: Frank Chen Date: Mon, 31 Aug 2026 19:22:31 +0000 Subject: [PATCH] docs(java): correct step attempt numbering --- docs/sdk-reference/operations/step.md | 4 ++-- docs/testing/api-reference.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/sdk-reference/operations/step.md b/docs/sdk-reference/operations/step.md index 88d1f4a..7b5d9bd 100644 --- a/docs/sdk-reference/operations/step.md +++ b/docs/sdk-reference/operations/step.md @@ -239,13 +239,13 @@ The step will checkpoint the last error after exhausting all retry attempts. ```java interface StepContext { DurableLogger getLogger(); - int getAttempt(); // current retry attempt, 0-based + int getAttempt(); // current retry attempt, 1-based } ``` - `getLogger()` A logger enriched with execution context metadata. See [Logging](../observability/logging.md). - - `getAttempt()` The current retry attempt number (0-based). + - `getAttempt()` The current retry attempt number (1-based). Java `StepContext` does not expose replay state. Use `DurableContext.isReplaying()` in orchestration code outside the step function. diff --git a/docs/testing/api-reference.md b/docs/testing/api-reference.md index f828a4f..248f00e 100644 --- a/docs/testing/api-reference.md +++ b/docs/testing/api-reference.md @@ -1007,7 +1007,7 @@ shared set of accessors. // Step error ErrorObject getError() - // Retry attempt number (0-based) + // Retry attempt number (1-based) int getAttempt() ```