Asynchronous polling with Splitter in Re-assemble Messages mode

[Glico21]

Asynchronous polling with Splitter in Re-assemble Messages mode

Description

When using several simultaneous asynchronous calls to a single flow that contains Splitter in Re-assemble Messages mode, all messages from previous flow calls are collected in Splitter in the last called flow. Even if Splitter is configured so that each individual flow call has a unique GroupID, messages from all previous calls will be collected in the last called flow.
Reproduced an issue in this flow.

1. Webhook. Gets unique id and number of calls to API
2. Splitter in Split JSONata Expression mode. Creates an array of ids to send to API
3. REST API. Sends request to the API
4. Splitter in Re-assemble Messages mode. Gathers responses from the API into one group with the id received from the Webhook.
   If several simultaneous asynchronous calls to this flow, the last of the called flow collects all messages received from other flows and continues the flow. All previously started flows remain on the step before Splitter in re-assemble mode and time out.

Component Version

Latest Splitter version: v1.4.3(73d0341)

Steps to Reproduce

1. Make several simultaneous calls of this flow
   
   
   
2. Look at the executions page. All but the last running flow will look like this.
   
   If you pay attention to the splitter logs, you can see that the group with the corresponding id is created
   
3. The last one will look like this.
   
   
   Here you can see in the Utility-component all three messages from previous calls to flow.
   
   In this case, the request-reply component is called 3 times, which is not correct, because the previous threads never received a reply and came timed out response.
   

Actual Result

One of our clients is not satisfied with this Splitter behavior because the runs of not the last flow contain unique id's for the whole flow to work correctly.

Workaround(s)

No known workarounds