Camunda resolving additional incidents

Hello, folks

I’m using Camunda 7.10.0 and find that service finished working incorrectly at some point so it created Incidents in Camunda using createIncident() method. Although Incident type is always defined in service, so it’s easier to understand what is wrong. I have different incidents on different processInstances and different Definition versions.
So, what I intended to do is resolve one of the incidents using Camunda REST API DELETE /incident/{id}
But as I do that - I get most of my Incidents resolved(Some were left), which I did not intended to resolve.
Note that those incidents that were resolved didn’t have id used in REST neither as cause_incident_id_ nor root_cause_incident_id_ .

I was wondering whether somebody stumbled upon a problem like this and have a decision for that.