The workflow triggered by cron node runs 3 times in parallel

Questions
1

Describe the problem/error/question

the workflow triggered by cron node runs 3 times in parallel

What is the error message (if any)?

Please share your workflow

![image|338x500](upload://1no1jfFvOGyPFIMzQW4b7nUAqfN.png)

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

image
image1278×477 58.6 KB

Share the output returned by the last node

Information on your n8n setup

  • **n8n version: 1.27.2
  • **Database (default: SQLite): postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • **Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • **Operating system: Amazon Linux 2

my wf triggers by cron at right time and runs 3 times in parallel, why would that happen?
at first i thought its the same wf, but the executions IDs are different and time of completion differs.
please note, that the same behavior is observed in different environment where n8n version is n8nio/n8n:1.53.0

please advise,

thank you in advance!

2

Have you tried restarting the n8n instance?

3

yes. the same behavior - it executes 3 times

4

Could you paste a screenshot of the trigger rules in your scheduler node?

5

image
image373×796 27.5 KB

6

Probably something funky with the saved triggers.
When you start n8n what does it show for workflows that are activated? does it show 3 times.
Also can you try disabling the workflow and see if it then runs twice?

7

yes, when workflow triggers by cron at correct time, it runs 3 times. time of execution and WF IDs are different.

image
image1290×365 35.3 KB

this is my main WF which triggers subworkflows which are running 3 times also.

yes, i have tried disabling wf, restarting n8n deployments, deleting cron node and creating new one - behavior remains the same, runs 3 times.

8

another thing i have tried is to change the cron scheduled time to another and save the wf. that WF was triggered at original time (old time) and at updated time… and both were running x3. i restarted deployment and it ran at new time only but still 3 times

9

Does this also happen with other workflows?

10

i have only one WF with cron node which behaves like that. other WF work fine

11

The idea I see here is to export the workflow json and import it in a freshly created one. Maybe that specific original workflow was somehow old triggers not deleted in db.

12

actually, we did it also. the WF in the screenshot i shared last is imported from scratch

13

the original time trigger was solved by restarting the n8n, but triple execution still takes place

14

is there anything else i could try?

15

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.