Implemented
0
Next scheduled workflow is executed before previous workflow has finished
Source: n8n-io/n8n#40540 · opened by @APT37
Bug Description
For scheduled workflows, the currently running worklow instance should block the next instance on the schedule from running.
To Reproduce
1. Create scheduled workflow that performs a long task
2. Wait until the next scheduled execution is triggered
3. Cry because they're now running in parallel and destroying your data
Expected behavior
Previous workflow blocks next if it's still running.
Debug Info
Not sure what to supply here.
Operating System
Ubuntu Linux 26.04
n8n Version
2.42.3
Node.js Version
Not sure how to check this
Database
SQLite (default)
Execution mode
main (default)
Hosting
self hosted
For scheduled workflows, the currently running worklow instance should block the next instance on the schedule from running.
To Reproduce
1. Create scheduled workflow that performs a long task
2. Wait until the next scheduled execution is triggered
3. Cry because they're now running in parallel and destroying your data
Expected behavior
Previous workflow blocks next if it's still running.
Debug Info
Not sure what to supply here.
Operating System
Ubuntu Linux 26.04
n8n Version
2.42.3
Node.js Version
Not sure how to check this
Database
SQLite (default)
Execution mode
main (default)
Hosting
self hosted
No pledges yet. Be the first to back this.
Comments
Similar requests
Workflow settings cannot unset callerIds after workflowsFromAList; exact restore is impossible
0 votes · 0 comments
Feature: cross-workflow agent memory — persistent verified memory for AI Agent nodes
0 votes · 0 comments
Agent skill spec-driven-development has no path for creating a spec
0 votes · 0 comments
Feature: Add configurable request-body validation to the Webhook node
0 votes · 0 comments
SQLite database file never shrinks after execution pruning/deletion — disk fills up despite pruning being enabled
0 votes · 0 comments
No comments yet.