We match the process with an id held in the internal system and use this id as the correlation key, since the message is published globally, we guarantee that it is unique, the service leaves a job to the queue via task workers, the consumer application that does this job tells another queue whether it is successful or not, then the consumer that reads this leaves a message to the Zeebe client and Camunda, Camunda listens to this message with a structure like the one below. The problem here is that the event based gateway cannot access local inputs because it does not wait directly on the catch event. (processing result and element id)
