If there's a boundary timer with execution listener for event end, is it expected behavior that a non-canceling boundary timer will trigger the event end? So I have a receive task with a non-canceling timer with 30s timer. After 30s, it will execute the
Is this expected behavior? I expected it to not trigger since non-canceling timer doesn't really end the receive task?
Also, I'm a little confused on the documentation for execution listener. It says for event="start", it will NOTIFY the execution listener when it starts but only EXECUTE/CALL the notify function when an end event occurs. Then it says the 3rd execution listener (event="end") in that example will be CALLED when it "ends".
Can you share the exact BPMN XML? When the receive task has an execution listener for the end event, I would expect it not to be triggered when there's a boundary event attached that doesn't cancel the activity.
Whoops, I didn't put it in code block so it got erased. Anyway, just a simple case. After 30Seconds, it executes the expression although the receiveTask hasn't ended.