-
Notifications
You must be signed in to change notification settings - Fork 396
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
bug: Early return not triggered on error in parallel branches beforehand #3865
Comments
Please provide a minimal reproduction and we will investigate |
Alright, so you can use the following one. If using parallel branches or not the behavior changes. Also if defining a own custom error handler or not changes the behavior. My expectation is that in no case (wether parallel or not, wether using a own error handler or not) the code in the last step is never run!
|
Another example where it WORKS AS EXPECTED with parallel branches and a customer error handler
|
Describe the bug
There are three parallel branches, which are for validation. They throw an error if something is invalid. After this parallel branches a early return is placed, which returns a empty result:
when a error happens the early return does not actually return, but the flow continues running and returns internal information, which should never be returned
To reproduce
Cannot provide you with a minimum reproducible flow (yet)
Expected behavior
...
Screenshots
No response
Browser information
No response
Application version
EE v1.334.0-1-g4d88dadb1
Additional Context
No response
The text was updated successfully, but these errors were encountered: