Skip to content

Commit 3019dfd

Browse files
sankari165jakobht
andauthored
Update src/docs/08-workflow-troubleshooting/03-retries.md
Co-authored-by: Jakob Haahr Taankvist <[email protected]>
1 parent 61136bb commit 3019dfd

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/docs/08-workflow-troubleshooting/03-retries.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ Read more about [activity retries](https://cadenceworkflow.io/docs/concepts/acti
1414

1515
One thing to note is how activity retries and workflow retries are shown in the Cadence Web UI. Information about activity retries is not stored in Cadence. Only the last attempt is shown with the attempt number.
1616

17-
Moreover, attempt number starts from 0, so Attempt:0 refers to the first and original attempt or Attempt:1 refers to the second attempt or first retried attempt.
17+
Moreover, attempt number starts from 0, so `Attempt: 0` refers to the first and original attempt, `Attempt: 1` refers to the second attempt or first retried attempt.
1818

1919
For workflow retries, when a workflow fails or times out and is retried, it completes the previous execution with a ContinuedAsNew event and a new execution is started with Attempt 1. The ContinuedAsNew event holds the details of the failure reason.
2020

0 commit comments

Comments
 (0)