Skip to content

W-18404398-until-successful-scope-rewrite-44-dm #3083

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
merged 1 commit into from
Jul 2, 2025
Merged

W-18404398-until-successful-scope-rewrite-44-dm #3083

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
6 changes: 3 additions & 3 deletions modules/ROOT/pages/until-successful-scope.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ Until Successful runs synchronously. If any processor
within the scope fails to connect or to produce a successful result,
Until Successful retries all the processors within it, including the one that failed, until all configured retries
are exhausted. If a retry succeeds, the scope proceeds to the next
component. If the final retry does not succeed, Until Successful produces an error.
component. If the final retry doesn't succeed, Until Successful produces an error.

Routing is successful if no exception is raised
or if the response matches an expression.
Expand All @@ -31,7 +31,7 @@ You can configure the following attributes in the Until Successful scope:
|===
|Field | XML | Description
|Max Retries | `maxRetries` |Specifies the maximum number of retries that are allowed. This attribute can be either a number or an expression that resolves to a number. An error message looks like this: `Message: 'until-successful' retries exhausted.` The Mule error type is `MULE:RETRY_EXHAUSTED`.
|Milliseconds Between Retries | `millisBetweenRetries` |Specifies, in milliseconds, the minimum interval between two retries. The actual interval depends on the previous execution, but it should not exceed twice this number. The default value is 60000 milliseconds (one minute). This attribute can be either a number or an expression that resolves to a number.
|Milliseconds Between Retries | `millisBetweenRetries` |Specifies the minimum interval, in milliseconds, between retries. The actual interval depends on the duration of the previous attempt, but it shouldn't exceed twice this value. The default is `60000` (one minute). This attribute can be either a number or an expression that resolves to a number.
|===

== Example Configuration of the Until Successful Scope
Expand Down Expand Up @@ -89,7 +89,7 @@ The next processor after the Until Successful scope executes, in this case, the

== Variable Propagation

Every execution of the Until Successful scope starts with the same variables and values present before the execution of the block. New variables or modifications to already-existing variables while processing one element are not visible in the next execution (in case there is an error). If the execution finishes correctly, the variables (and payload) are propagated to the rest of the flow.
Every execution of the Until Successful scope starts with the same variables and values present before the execution of the block. New variables or modifications to already-existing variables while processing one element aren't visible in the next execution (in case there is an error). If the execution finishes correctly, the variables (and payload) are propagated to the rest of the flow.

== See also

Expand Down