flowable / flowable-engine

A compact and highly efficient workflow and Business Process Management (BPM) platform for developers, system admins and business users.
https://www.flowable.org
Apache License 2.0
8k stars 2.62k forks source link

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

Open LIXNA opened 3 months ago

LIXNA commented 3 months ago

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 commented 3 months ago

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

LIXNA commented 3 months ago

Environment: Java17, flowable 7.0.1

C-DOUBLE-J commented 3 months ago

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 commented 3 months ago

image image

LIXNA commented 3 months ago

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