Environment (Required on creation): Production

Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket):

We create incidents on intermediate message receive events in order to keep track of messages that fail to arrive for "a long time". We have implemented that behavior to see an incident in those process instances which are laying around for a long time, because they may be waiting for messages that never will arrive. We are monitoring the incidents in the engine in order to notify administrators about these process instances. When an administrator fixes the cause of the problem and the message for a dedicated process instance finally arrives, all incidents in all process instances are being resolved too.

Steps to reproduce (Required on creation):

#1 Run the provided process application
#2 Start an arbitrary number of process instances (credentials admin, admin)
#3 Create an incident for all process instances. Replace {insert-execution-ids-here} in curl request.

curl --request POST \
  --url http://localhost:8080/engine-rest/execution \
  --header 'Content-Type: application/json' \
  --data '{
"processDefinitionKey":"incident-bug-report-process",
    "activityId":"Event_10w5f18",
"sorting":
    [

,
   

]
}'

curl --request POST \
  --url http://localhost:8080/engine-rest/execution/\{insert-execution-ids-here}/create-incident \
  --header 'Content-Type: application/json' \
  --data '

'

#4 Correlate a message to exactly one of the process instances. Replace {process-instance-id} with your actuall process instance id.

curl --request POST \
  --url http://localhost:8080/engine-rest/message \
  --header 'Content-Type: application/json' \
  --data '

'

#5 Witness all created incidents dissappearing for all process instances.

Observed Behavior (Required on creation):

All created incidents dissappearing for all process instances

Expected behavior (Required on creation):

Only incidents related to given processinstance is being resolved. 

Root Cause (Required on prioritization):

Solution Ideas (Optional):

Hints (optional):