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

Boundary timed event ,If at the end, the end event cannot be triggered,The listener did not detect it #3950

Open
LIXNA opened this issue Aug 17, 2024 · 5 comments

Comments

@LIXNA
Copy link

LIXNA commented Aug 17, 2024

Describe the bug
A clear and concise description of what the bug is.

Expected behavior
A clear and concise description of what you expected to happen.

Code
If applicable, add the code that you are using when having the issue.

Additional context
Add the version of Flowable that you are using, the database vendor and if you are using Flowable within Spring Boot, the Flowable Task application etc.
If at the end, the end event cannot be triggered
8b7fb85968ad4e34105e509a8f8310f

@LIXNA
Copy link
Author

LIXNA commented Aug 17, 2024

Jumping to the next node also jumps to the line, not to the shutdown event

@LIXNA
Copy link
Author

LIXNA commented Aug 17, 2024

Environment: Java17, flowable 7.0.1

@C-DOUBLE-J
Copy link

I encountered a similar issue with my Flowable configuration using a synchronous executor. In the normal workflow, I can successfully retrieve the execution listener for the end event when it is reached. However, when I trigger a boundary timer from a user task and then reach the end event, an exception is thrown because the original end event's listener cannot be retrieved.

@C-DOUBLE-J
Copy link

image
image

@LIXNA
Copy link
Author

LIXNA commented Aug 22, 2024

I encountered a similar issue with my Flowable configuration using a synchronous executor. In the normal workflow, I can successfully retrieve the execution listener for the end event when it is reached. However, when I trigger a boundary timer from a user task and then reach the end event, an exception is thrown because the original end event's listener cannot be retrieved.

Non interruptive Can be executed,But sometimes the job listener cannot detect success or failure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants