Skip to content

Commit bac05dc

Browse files
Update specification.md
Co-authored-by: Ricardo Zanini <[email protected]>
1 parent f3a3e0c commit bac05dc

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

specification.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4670,7 +4670,7 @@ The `when` property defines the specific errors to handle. Allows for handling o
46704670

46714671
The `exceptWhen` property defines the specified errors NOT to handle. Allows for handling all errors, excluding specific ones.
46724672

4673-
The `retry` property serves to either reference an existing retry policy or define a new one to be employed when handling specified errors within the workflow. If a retry policy is designated, the error source identified by the [error source](#error-source) will undergo retries according to the guidelines outlined in the associated [policy](#retry-definition). In the event that a retry attempt is successful, the workflow seamlessly proceeds as though the error had not transpired. However, if the maximum number of configured retry attempts is exhausted without success, the workflow proceeds to execute the error outcome stipulated by the `then` property.
4673+
The `retry` property serves to either reference an existing retry policy or define a new one to be employed when handling specified errors within the workflow. If a retry policy is designated, the error source identified by the [error source](#error-source) will undergo retries according to the guidelines outlined in the associated [policy](#retry-definition). If a retry attempt is successful, the workflow seamlessly proceeds as though the error had not transpired. However, if the maximum number of configured retry attempts is exhausted without success, the workflow proceeds to execute the error outcome stipulated by the `then` property.
46744674

46754675
The `then` property defines caught errors outcome, if any. If not defined, caught errors will be considered as handled, and the execution of the workflow will continue as if the error never occured. Handled errors that are not [rethrown](#error-outcome-definition) do NOT [bubble up](#error-bubbling).
46764676

0 commit comments

Comments
 (0)