Scheduled Workflows executed twice

Questions
1

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 version: 1.49.0
  • Database (default: SQLite): postgres
  • n8n EXECUTIONS_PROCESS setting: regular
  • Running n8n via : docker (self-hosted)
2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

Hi @DigiP

Thanks for posting here and welcome to the community! :raised_hands:

Could you share your workflows? What other nodes are contained in these?
Can you confirm you only see this happening for workflows with Schedule Triggers?
Also, what does your docker configuration look like? Can you confirm you only have one n8n instance talking to the database?

Thanks! :pray:

4

Hi ria,

thanks for the warm welcome :slight_smile:

I use those workflows for work, so I cannot share everything due to confidentiality reasons. I am currently trying to reproduce the problem with simple workflow that I can share.

The problem of multiple executions also sometimes happens, when I just press the “test workflow” button, but not every time. Reloading the page seems to fix it.

It feels a bit as if a cron job or something like that is stuck sometimes. I have a different case, where I have a workflow that as a Schedule trigger, was active for a while, but is now set to “inactive”. I would expect it to not run anymore, but it still does. I think this could be related.

I think it is just one n8n instance talking to the n8n database.

Do you have any ideas, what the problem could be?

5

Hi @DigiP

as a matter of fact we have just released a new beta version and included a potential fix:

If you would be willing to update to that and test it, we’d be happy to know if that solves it! :crossed_fingers:

1 Like
6

Hello,

sorry, it took us a while to update… We are now on version 1.53.2 (the change should be in there, right?).
But the tasks are still executed twice. I even tried changing the timing by a minute and saving the workflow again. But now there are still two executions. One at the original time and one that I changed by one minute. It seems as if there is a cron job stuck somewhere (i have also cases, where an old version of the workflow gets executed).

I was also able to reproduce the bug with a very simple workflow that is just a schedule trigger and a Slack node that posts a message to a channel (this workflow was set up before the update).

Any ideas? I could also try to delete the workflows with problems and rebuild them, maybe that helps?

7

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