Task does not await incomming message flows after resumed at breakpoint.

[frasalSyc]

Describe the Bug

Trigger Event at Breakpoint: Task does not await incoming message flows

Steps to Reproduce

Model two Processes with connected Tasks (incoming and outgoing Message Flows). See example.
Set a Breakoint to Task A
Launch both Processes (Task B first)
Trigger Event at Task A
Outgoing Message Flows will be triggered, but incoming Message flows will not be awaited at the task resumed at breakpoint..

Expected Behavior

Task manually triggered at breakpoint should have the same behaviour as without breakpoint: Send message Tokens to outgoing message Flows and await message Tokens from incoming message Flows in the order from left to right. No matter, the incoming is the first or the following flow.

Environment
Camunda Modeler system information

Version: 5.31.0
Operating System: Windows 10 amd64
Plugins: bpmn-js Token Simulation
Execution Platform: BPMN - Camunda 7

[barmac]

@nikku to look into this.

[nikku]

@frasalSyc Thanks for the report. This indeed is a bug that has to be fixed in the upstream token simulation project.

From the perspective of Task A, there is two things to do in sequence: (1) trigger the message, (2) produce an outgoing token.

[frasalSyc]

@nikku If you start Proc A without a Breakpoint in Task A, Task A triggers a Message. Assumed Task B is having the Token, Task B awaits the incoming Message and returns a Message Token back to Task A. Task A waits for this incoming Message an then the Token goes to End. Waiting for Incoming Message does not happen, if Task A Breakpoint is enabled.