There are situations when two conflicting shadows may be present in midPoint repository. E.g. corner cases such as
MID-4389 or (more likely) misconfigurations (e.g. matching rule misconfiguration). Those shadows in fact represent the same resource object and they should be somehow cleaned up. Currently, presence of conflicting shadows is a lethal poison for midPoint and the model process cannot recover from this. We need a way how to recover automatically.