Skip to Content
Flower 3.7.1 is released 🎉 See what's new
DocsDeveloper ReferenceSpecificationsModeling Hints (bpmnlint)
Developer Reference· 3 min read· Updated November 2026

Modeling Hints (bpmnlint)

bpmnlint  is the open-source linter for BPMN diagrams of the bpmn.io project. The modeler of Flower BPM uses its recommended rules to show hints while you draw, for example a gateway that splits and joins at once, or a task with two incoming flows that looks like a join.

The hints are released site by site. They never block a model: every rule is a warning, and the model validation rules decide whether a model can be published.

Some recommended rules of bpmnlint are switched off, because they contradict what Flower BPM executes or allows. The reason is in the table.

Generated from bit.flower master by util/generate-specs.mjs. Do not edit this section by hand.

18 rules are on (all as warnings: nothing blocks), 8 are off on purpose.

RuleIn Flower BPMWhat it checks
conditional-flows WarningChecks that sequence flows outgoing from a conditional forking gateway or activity are either default flows or have a condition attached
end-event-required WarningChecks the presence of an end event per scope.
event-sub-process-typed-start-event WarningChecks that start events inside an event sub-process are typed.
fake-join WarningChecks that no fake join is modeled by attempting to give an element join semantics, i.e. a task or event with multiple incoming flows, or a link catch event targeted by multiple link throw events. Users should model a parallel joining gateway to achieve the desired behavior.
label-required WarningChecks the presence of a label.
no-complex-gateway Warning
no-disconnected WarningA rule that verifies that there exists no disconnected flow elements, i.e. elements without incoming or outgoing sequence flows.
no-duplicate-sequence-flows WarningA rule that verifies that there are no disconnected flow elements, i.e. elements without incoming or outgoing sequence flows.
no-gateway-join-fork WarningChecks that, whether a gateway forks and joins at the same time.
no-implicit-split WarningChecks that no implicit split is modeled starting from a task. Users should model the parallel splitting gateway explicitly instead.
no-overlapping-elements Warningelement: ModdleElement, left: number, right: number, top: number, bottom: number } } Shape
single-blank-start-event WarningChecks that whether not more than one blank start event exists per scope.
single-event-definition WarningA rule that verifies that an event contains maximum one event definition.
start-event-required WarningChecks that for the presence of a start event per scope.
sub-process-blank-start-event WarningChecks that start events inside a normal sub-processes are blank (do not have an event definition).
superfluous-gateway WarningChecks that, whether a gateway has only one source and target. Those gateways are superfluous since they don’t do anything.
superfluous-label WarningChecks that unconditional sequence flows do not have a label. Labels are only meaningful on sequence flows forking out of XOR/OR gateways, on conditional flows, and on default flows. Anywhere else they duplicate information already conveyed by the diagram.
superfluous-termination WarningChecks that, whether a gateway has only one source and target. Those gateways are superfluous since they don’t do anything.
no-inclusive-gateway Off: Flower executes inclusive gateways (OR split and join)
no-implicit-end Off: a task without an outgoing flow ends its branch, Flower handles that (the process ends when no branch is running)Checks that an element is not an implicit end (token sink).
no-implicit-start Off: the Flower validator has its own rule for nodes without an incoming flowChecks that an element is not an implicit start (token spawn).
no-bpmndi Off: models imported from other tools may lack diagram information for single elements
ad-hoc-sub-process Off:A rule that ensures that an Ad Hoc Sub Process is valid according to the BPMN spec: - No start or end events
event-based-gateway Off:Checks that, whether an event-based gateway: - has at least two outgoing sequence flows - the outgoing sequence flows are not conditional
link-event Off:A rule that verifies that link events are properly used. This implies: * for every link throw there exists a link catch within the same scope, and vice versa * there exists only a single pair of [ throw, catch ] links with a given name, per scope * link events have a name
global Off:A rule that verifies that global elements are properly used. Currently recognized global elements are: * bpmn:Error * bpmn:Escalation * bpmn:Message * bpmn:Signal For each of these elements proper usage implies: * element must have a name * element is referenced by at least one element * there exists only a single element per type with a given name
Last updated on