Cannot correlate message '<message name>': No process definition or execution matches the parameters

Hi @Hammad_Dar,

normally, when you check the send task with async before and the receive task not and both are behind a parallel gateway, the message event and the job are created together in a single commit the database. After this commit, the engine will execute the job and the message will be sent (The receive event is already available in the database).

I have discussed this with other customers for a single parallel gateway.

But I don’t know if any optimization with the nested parallel gateway can disturb this behaviour in your case.

To analyze the behaviour further, you can set these logging levels to DEBUG

org.camunda.bpm.engine.persistence
org.camunda.bpm.engine.cmd
org.camunda.bpm.engine.bpmn.behavior

They will provide you a lot of information, when you run the complete process multiple times. But the relevant lines are these:

19:28:41.137 [main] DEBUG org.camunda.bpm.engine.persistence - ENGINE-03009 SQL operation: 'INSERT'; Entity: 'MessageEntity[id=21]'
19:28:41.138 [main] DEBUG org.camunda.bpm.engine.persistence - ENGINE-03009 SQL operation: 'INSERT'; Entity: 'MessageEntity[id=28]'
19:28:41.139 [main] DEBUG org.camunda.bpm.engine.persistence - ENGINE-03009 SQL operation: 'INSERT'; Entity: 'EventSubscriptionEntity[id=24]'
19:28:41.139 [main] DEBUG org.camunda.bpm.engine.persistence - ENGINE-03009 SQL operation: 'INSERT'; Entity: 'EventSubscriptionEntity[id=31]'

where the MessageEntity is the job created for the async before and the EventSubscriptionEntity is the receive task.

You can check for further changes on the IDs to localize the root cause.

Hope this helps, Ingo

So what about the issue I am facing? I frankly see things little tricky around this area in this scenario. As per the code I have seen, it is correlating the message and failing most probably due to the fact that Receive Task is not yet created. Please do share some material to read or refer this to someone who could help.

Anyone who can help in this regard?

@Hammad_Dar
Any news about your exception ?
I have the same exception with parrallel receive task :frowning:

Capture