Guide / Every rule
Ad-hoc sub-process without an activity
The check compat/ad-hoc-sub-process, in the group Engine compatibility.
Why it matters
An ad-hoc sub-process with nothing in it has nothing for the engine to run, so the instance can never complete it.
How to fix it
Add at least one activity to the ad-hoc sub-process, or delete 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/ad-hoc-sub-process. 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/ad-hoc-sub-process or compat/ad-hoc-sub-process to off in your .bpmnlintrc. See Validation.
Rule details
| Id | compat/ad-hoc-sub-process |
| Group | Engine compatibility |
| Level | Error: the diagram or the process is wrong |
Read more: Validation. All rules: Every rule.