Guide / Every rule

Escalation boundary event on the wrong element

The check compat/escalation-boundary-event-attached-to-ref, in the group Engine compatibility.

Error

Why it matters

Escalations are raised inside a sub-process or a call activity, so a boundary event on any other element never catches one.

How to fix it

Attach the escalation boundary event to a sub-process or call activity.

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/escalation-boundary-event-attached-to-ref. 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/escalation-boundary-event-attached-to-ref or compat/escalation-boundary-event-attached-to-ref to off in your .bpmnlintrc. See Validation.

Rule details

Read more: Validation. All rules: Every rule.