Guide / Every rule
Start timer set in the past
The check compat/timer-past-date, in the group Engine compatibility.
Why it matters
A timer start event whose date, or whose cycle start, is already past fires right after deployment, and a cycle then runs from the deployment time.
How to fix it
Use a future date, or a cron expression to run on a fixed schedule.
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/timer-past-date. 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/timer-past-date or compat/timer-past-date to off in your .bpmnlintrc. See Validation.
Rule details
| Id | compat/timer-past-date |
| Group | Engine compatibility |
| Level | Advice: it works, and reads or runs better without it |
Read more: Validation. All rules: Every rule.