Prevent simultaneous workflow executions with Redis
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 7 nodes and runs on a schedule (every 5 seconds). Along the way it connects Redis.
How it runs
Trigger: On a schedule (every 5 seconds).
- Get Flag (Redis): get
- Flag does not exists (Filter): keeps only the items that match a condition
- Set Flag (Redis): set
- Execute Workflow (Execute Sub-workflow): calls another n8n workflow
- Remove Flag (Redis): delete
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (5)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Execute Sub-workflow
n8n-nodes-base.executeWorkflow - Redis
n8n-nodes-base.redis - Filter
n8n-nodes-base.filter - No Operation, do nothing
n8n-nodes-base.noOp
From the author
Purpose This ensures that executions of scheduled workflows do not overlap when they take longer than expected. How it works - This is a separate workflow which monitors the execution of the main workflow - Stores a flag in Redis (key dynamically named after…