{
“type”: “RestException”,
“message”: “org.camunda.bpm.engine.MismatchingMessageCorrelationException: ENGINE-13031 Cannot correlate a message with name ‘ShivaKnows’ to a single execution. 2 executions match the correlation keys: CorrelationSet [businessKey=22, processInstanceId=null, processDefinitionId=null, correlationKeys=null, localCorrelationKeys=null, tenantId=null, isTenantIdSet=false]”
}
I see 19 processes. The blue Icon is on the gateway. I am trying to call the message called Shivaknows. It is telling me the following
{
“type”: “RestException”,
“message”: “org.camunda.bpm.engine.MismatchingMessageCorrelationException: ENGINE-13031 Cannot correlate a message with name ‘ShivaKnows’ to a single execution. 2 executions match the correlation keys: CorrelationSet [businessKey=22, processInstanceId=null, processDefinitionId=null, correlationKeys=null, localCorrelationKeys=null, tenantId=null, isTenantIdSet=false]”
}
This means that you have 2 instances that match the message so the sending fails.
You can add all = true to your rest call and it will trigger everything.
The reason you don’t see anything in tasklist is because you don’t have any Human Tasks.
I am trying to understand what an instance means. I am firing these commands from postman as you saw. I have a User task that says answer the question. In your tutorial, I saw that you were seeing a whole bunch of tasks. I have somewhat replicated your tutorial with some very minor modifications. thats all.
If there is an instance waiting on the event based gateway - only a message can move the token further.
If you saw a token waiting at the user task, it would mean that the user task has been activated and it would be visible in tasklist.
At the moment - from what you’ve said you haven’t been able to successfully send a message and so the process has not moved on to the user task and therefore is has not been activated.
There is no business key being given to the message. How I can I attach a business key to this message like I do from post man.
Keep in mind that MessageEvent process calls the payment process by send a message shown above.