Skip to content
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.

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

W-11599455 try scope revamp and ref duke #2386

Open
wants to merge 10 commits into
base: v4.4
Choose a base branch
from
Prev Previous commit
Update modules/ROOT/pages/try-scope-concept.adoc
dukesphere authored Oct 20, 2022
commit 3f19b2258c9cd0f1717ff988db74eaab53afae78
2 changes: 1 addition & 1 deletion modules/ROOT/pages/try-scope-concept.adoc
Original file line number Diff line number Diff line change
@@ -194,7 +194,7 @@ After a component within the Try scope raises an exception, any subsequent compo
Each error handling strategy in a Try scope (`on-error-*`) follows a condition. This condition is typically an error type (or a list of several) which must match the current error. You can also define this condition as a DataWeave expression, such as `error.cause.message.contains("fatal")`.

[NOTE]
Conditions are evaluated in order and only the first strategy to match is executed.
Conditions are evaluated in order, and only the first strategy to match is executed.

Below is an example that includes two error handling strategies, each executing a logger component: