Hi Manuel,

The issue you’re encountering with the Conformance Checker likely arises from the tool’s interpretation of the parallel paths in your BPMN model. The Conformance Checker can sometimes struggle with models that use parallel gateways (AND gateways) because it expects a strict sequence of activities, whereas your model allows for some activities to occur independently and in parallel. Thus, if an activity appears more than once within the same variant, the second occurrence will be flagged as a violation.

To address this, you could consider using self-loops for activities that might occur multiple times. In a parallel gateway, each path can happen once in any order. However, if some activities repeat, adding self-loops allows the Conformance Checker to recognise these repetitions as valid. Without self-loops, repeated occurrences might be flagged as violations.

Hope this helps!

Hi Sakura,
thanks for the reply. 
The self loops are no option actually as I indeed want to flag multiple occurences of the same activity as violations.

 However a finding I made in the meantime is that I was mainly mislead by the title. e.g. “C followed by D” was actually a violation as on a more detailed look as those flagged variants had C→ D → B so B was not happening at the correct position. That being said in the newly updated Process Adherence Manager the violations are more “verbose” indicating clearer what the issue is.