-
Bug Report
-
Resolution: Cannot Reproduce
-
L3 - Default
-
None
-
None
-
None
Environment (Required on creation):
Camunda Run 7.16.0-ee
Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket):
When i created a process which has a conditional boundary event on a user task, even when the condition is met - the boundary event does not fire.
Not matter if the condition is present when the task is reached or the condition happens after the task is reached.
Steps to reproduce (Required on creation):
Deploy the process uploaded (along with the form if you're feeling fancy)
Start the process from task list and add a variable called "stop" as a boolean set to true. (this is the condition on the event)
Click Start.
Observed Behavior (Required on creation):
The task appears in tasklist
Expected behavior (Required on creation):
The task should have been canceled by the event and should have interrupted.
Root Cause (Required on prioritization):
Solution Ideas (Optional):
Hints (optional):
I tested this on 7.15.0-ee and it worked as expected.
Hey niall.deehan,
thanks for bringing this up and providing all the necessary details already!
We'll try to reproduce and root cause this as soon as possible.
Thanks and stay tuned,
Tobias