carsten
Setembro 17, 2025, 5:34pm
3
I am getting double executions all the time and you will find old/ancient posts here begging for a better cronjob.
Hello,
I have a few workflows that are triggered by a schedule trigger once a day at a certain time.
When I check the “executions” tab, I see, that some workflows are triggered twice at the same time.
I would like to prevent this, because it slows down the performance and sometimes causes problems in the workflows.
Does anyone know why this is happening and how I could fix this?
I already tried deleting the schedule trigger node and creating a new one.
Information on your n8n setup
n8n ve…
master ← global-registry-cron
opened 09:30AM - 12 Jul 24 UTC
## Summary
Letting individual nodes manage CronJob
1. creates a lot of duplic… ate code
2. adds the responsibility of cleaning up on the nodes
3. doesn't give us a centralized overview of all active CronJobs in the process
This PR aims to centralize how we register cronJobs, to have a better control over their lifecycle.
## Review / Merge checklist
- [x] PR title and summary are descriptive
- [x] Tests included
Describe the problem/error/question
Is there a possibility that n8n detects already executed items and just skip them? Let me give you more details:
I am the developer of the “SeaTable” node. SeaTable is comparable to Airtable, so it is a no code database where you can define your database structure in a browser and store all kind of data in it.
Currently I am improving the node and I want to add a new trigger like “New file / image”. This trigger should watch file/image columns and if there …
and so on…..
using n8n to schedule and trigger subworkflows to me only works when workers are disabled and n8n is in regular and not in queue mode . but i think this would no longer allow subworkflows at all.