Guide / Every rule

Interrupting event sub-process in an ad-hoc sub-process

The check compat/no-interrupting-event-subprocess, in the group Engine compatibility.

Error

Why it matters

An event sub-process inside an ad-hoc sub-process cannot interrupt it, so an interrupting start event is refused.

How to fix it

Make the start event of the event sub-process non-interrupting.

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-interrupting-event-subprocess. 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-interrupting-event-subprocess or compat/no-interrupting-event-subprocess to off in your .bpmnlintrc. See Validation.

Rule details

Read more: Validation. All rules: Every rule.