Guide / Every rule

Loop that never waits

The check compat/no-loop, in the group Engine compatibility.

Error

Why it matters

A cycle made only of tasks and gateways that run at once never waits for anything, so the instance spins in it and never stops.

How to fix it

Put an element that waits into the loop, such as a user task or a timer, or give it a gateway condition that leaves it.

Where you see it

The Problems tab lists it under Engine, the editor marks the element on the canvas, and penstock check reports it as compat/no-loop. It checks the diagram against the engine and the version it is written for: the version in the file's modeler:executionPlatformVersion, or the newest one when the file has none. Operaton and CIB seven are checked as Camunda 7. This check is free.

To turn it off, set camunda-compat/no-loop or compat/no-loop to off in your .bpmnlintrc. See Validation.

Rule details

Read more: Validation. All rules: Every rule.