`no-loop` Rule Detects False Positives

[philippfromme]

The no-loop rule aims to detect potential loops. These can also include call activities. If a call activity calls its parent process, it can cause an endless loop. The no-loop rule mirrors the behavior of Zeebe and only reports an error if the called process ID is the same as the parent process ID. However, it also reports an error if the call activity is part of a potential loop regardless of the process it calls. This process deploys without errors:

Reported through Slack: https://camunda.slack.com/archives/C0693F1NFK5/p1707223390238339

Related to camunda/camunda#13056

[nikku]

Moving to backlog. Not our current focus.