I am stuck at the receive task action. I’ve tried many ways to say to the engine that the message is received, but I am failing so hard. Most of the times I receive a report like
org.camunda.bpm.engine.MismatchingMessageCorrelationException: Cannot correlate message 'fpiComplete': No process definition or execution matches the parameters
I have already read message and task documentation, have already tried the snippets there, have already tried different ways to do that with the Runtime Service, have already tried to follow as this and I am still not able to complete my receive task.
There is an Advice in Receive Task documentation warning this:
Correlation of a parallel multi-instance isn’t possible because the subscription can’t be identified unambiguously.
It can be related to my problem? I mean, I am not using multi-instance, or are the parallel gateway splits considered as multi instances?
At a glace it looks like you’ve added a bunch of Asynchronous Before/After on tasks. This would complete the transaction and create a job for the enjoy to pick up.
During testing the engine’s job executor is turned off wouldn’t pick them back up. You need to explicitly complete the job before it will more to the receive task.
Take a look at these docs for more details:
You are right, It was needed to complete the job. Your comment was really helpful and it led me to study a series of new subjects that I had not studied at camunda.
Now I have explicitly executed the job, and I could correlate my message.
In my understanding, it should work, and the active token should continue till the end, but in fact, what is happening is that my process still waits at my Receive Task.