Camunda internal error

[hopetes]

**Issue Description: **
When receiving messages from external sources via API, an error occasionally occurs within the Camunda engine, specifically with "unknown source" message correlation. This happens even when the message name is correct, and the correlation message is valid. I suspect that this issue is caused by a bug within the Camunda engine itself.

Additionally, when two or more messages are sent to Camunda concurrently, it results in an error that causes the message correlation to fail, leading to the workflow becoming stuck. This is especially problematic when the message is mandatory, as it prevents proper message correlation and halts the process workflow.

**Problem: **

Sometimes, the process workflow becomes stuck due to mandatory messages not being correlated properly because of this issue.

**Possible recommendation: **

Please investigate the message correlation function within the Camunda engine. Also, check the directory used in the repository here: Camunda Directory. Additionally, concurrency handling in message processing may require improvement.

Trying with another BPM engine is also possible option.
The following screenshot could help to examine the errors that happen once in a while.

For more information look at the following recorded generated error.

issue-recorded.txt