Incorrect Schedule Behavior for Intervals Over 60 Minutes #14056
Description
Bug Description
When configuring the Schedule Trigger with an interval longer than 60 minutes (for example, 65 minutes), the workflow still triggers every 60 minutes, precisely at the start of each hour (:00 minutes). This behavior suggests that the scheduler might be incorrectly resetting or rounding the timer interval, causing the trigger to align with the beginning of the hour instead of respecting the set interval.
To Reproduce
- Create a new workflow in n8n.
- Add a Schedule Trigger node.
- Set the interval to a value greater than 60 minutes (e.g., 65 minutes).
- Activate the workflow and monitor the trigger times.
- Notice that the workflow triggers every 60 minutes exactly at :00 minutes instead of every 65 minutes.
Workflow example:
{
"nodes": [
{
"parameters": {
"rule": {
"interval": [
{
"field": "minutes",
"minutesInterval": 65
}
]
}
},
"type": "n8n-nodes-base.scheduleTrigger",
"typeVersion": 1.2,
"position": [
0,
0
],
"id": "62e7eb09-3879-4541-ba79-505ecb56dd3b",
"name": "Schedule Trigger"
},
{
"parameters": {
"assignments": {
"assignments": [
{
"id": "0f3a0dbb-ee1b-49d4-901c-d0b238f6e021",
"name": "test",
"value": true,
"type": "boolean"
}
]
},
"options": {}
},
"type": "n8n-nodes-base.set",
"typeVersion": 3.4,
"position": [
220,
0
],
"id": "b32b5226-7a57-4534-a0a4-4967ea2d7485",
"name": "test"
}
],
"connections": {
"Schedule Trigger": {
"main": [
[
{
"node": "test",
"type": "main",
"index": 0
}
]
]
}
},
"pinData": {},
"meta": {
"instanceId": "1b5c79f2248f81344ed0321b939c5a95254fa8a25526cfa35d2c6d5bebacb9b8"
}
}Expected behavior
The workflow should trigger based on the defined interval (e.g., every 65 minutes) from the moment of the first execution, without being aligned to the start of the hour.
Operating System
Ubuntu Linux
n8n Version
1.83.2
Node.js Version
actual
Database
PostgreSQL
Execution mode
queue