Invalid cron expression in n8n
- Feb 13
- 1 min read
What this means (non-technical)
A cron expression controls when a scheduled workflow runs. If the expression is malformed or incorrectly structured, the workflow may run at the wrong time, or not at all.
The schedule may look correct at a glance, but behave differently in practice.
What usually goes wrong
Common issues include:
Using the wrong number of fields.
Misunderstanding day-of-week numbering.
Setting impossible date combinations.
Typing special characters incorrectly.
And as a result:
Workflows never trigger.
They run more often than expected.
They run at unexpected times.
This can quietly disrupt reports, sync jobs, or time-based automations.
When this becomes urgent
This becomes urgent when:
Workflows handle time-sensitive data.
Reports must run at exact times.
Production schedules differ from development.
You notice missed or duplicated runs.
The longer an incorrect schedule goes unnoticed, the more data inconsistencies can build up.
Detect issues in your n8n workflows
|
Definitions
Cron expression: A string that defines a recurring schedule using minute, hour, day, month, and weekday fields.
Scheduled workflow: A workflow triggered automatically at defined time intervals.
Disclaimer
This article highlights common patterns and risks seen in real-world n8n workflows. It’s meant to help you build more confidently and avoid surprises as your automation grows. Behavior can vary depending on your setup, version, and configuration.