it’s a matter of timing. The challenge of Message correlation is to deliver the message only when the token reached the message event.
You could follow the process instance in Cockpit. To handle the issue in real life, you have to react on the MismatchingMessageCorrelationException and maybe move the message into an error message queue of your messging infrastructure or ask the user to try to deliver the message later.
Thanks for your suggesion. I’ll try add try-catch and retry the message correlation. i have also checked the process instance in Cockpit and see the workflow stop on Message Correlation. you can see image bellow