Guide / Every rule
More than one blank start event in Camunda 8
The check compat/no-multiple-none-start-events, in the group Engine compatibility.
Why it matters
Camunda 8 accepts only one blank start event in a process, so a second one makes the deployment fail.
How to fix it
Keep one blank start event and give the others an event type, or split the process.
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-multiple-none-start-events. 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-multiple-none-start-events or compat/no-multiple-none-start-events to off in your .bpmnlintrc. See Validation.
Rule details
| Id | compat/no-multiple-none-start-events |
| Group | Engine compatibility |
| Level | Error: the diagram or the process is wrong |
Read more: Validation. All rules: Every rule.