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
Reset active sequence flows upon terminate end event activation #10789
Reset active sequence flows upon terminate end event activation #10789
Conversation
Test Results 948 files ± 0 948 suites ±0 1h 42m 6s ⏱️ - 2m 41s For more details on these failures, see this check. Results for commit 13d00b2. ± Comparison against base commit c5f0f0a. ♻️ This comment has been updated with latest results. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@remcowesterhoud looks good. 👍
I have one optional suggestion. Please have a look.
...ain/java/io/camunda/zeebe/engine/state/appliers/ProcessInstanceElementActivatingApplier.java
Outdated
Show resolved
Hide resolved
… completed After a terminate end event has been completed the flow scope should be completed as well. When there are active sequence flows this doesn't happen as we have checks preventing a flow scope from completing when there is any active element instance or active sequence flow. By resetting this when the terminate end event is completed we can pass this check.
64f5a93
to
13d00b2
Compare
bors merge |
Build succeeded: |
Successfully created backport PR #10821 for |
Description
After a terminate end event has been completed the flow scope should be completed as well. When there are active sequence flows this doesn't happen as we have checks preventing a flow scope from completing when there is any active element instance or active sequence flow. By resetting this on activation of the terminate end event we can pass this check.
Related issues
closes #10590
Definition of Done
Not all items need to be done depending on the issue and the pull request.
Code changes:
backport stable/1.3
) to the PR, in case that fails you need to create backports manually.Testing:
Documentation:
Please refer to our review guidelines.