Duplicated schedule trigger

Questions
,
1

Hey, everybody.

After a while my workflow started to trigger twice each time instead of once on a trigger.
This was either due to an increase in process time after the trigger or as a result of adding a cron expression.

I removed the cron expression and re-created the workflow, but the situation remains the same. To me, this is a rather complicated issue that is unclear how to resolve.

n8n version 1.39.1, installed on the server. Updated it today.

  • n8n version: 1.39.1
  • Database: Supabase
  • n8n EXECUTIONS_PROCESS setting: default
  • Running n8n via: Docker
  • Operating system: Windows 10, 22H2, 19045.4355
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

Thank you, the information has been added.

4

Hi @Hurricanenik

Welcome to the community!

Can you share your workflow?

5

Hello,

So, I can assume it has to do with the processing time of the process. The first query in openai is text generation. The second one is generating an image.
This process takes about 2, 2.5 minutes total until it gets to the database update.

But the same error never happens during a test run or if I run this process on a trigger from telegram.

6

Does it trigger the second time after a minute or something like that?
Or directly 2 at the same time?

7

It was both.

image

Or like this…
Unbenannt2

8

that is basically the same time yes.
Can you disable the flow and see if you then have only 1 trigger?

9

I occationally have this issue. I think it’s related to a bug while saving the workflow, that will cause this duplication.

The solution (for me) is to restart the container.

1 Like
10

Checked the trigger’s operation. There are no messages when workflow is switched off.

11

I apologise for this question, to do this, do I need to use command sudo docker compose up -d?

12 
docker restart <container-name>

should be enough (I usually do it in portainer web-gui)

docker ps

shows the running container

3 Likes
13

Thank you for the commands. I’m using Putty and wanted to clarify, does this mean that the container are successfully restarted?

image

14

So after a few days of testing there is definitely an improvement. The trigger no longer duplicates the launch at or near the same time. :tada:

But the execution list now shows an execution at 00.00.00.00 every day. If you open this execution, there is nothing executing there, ie it looks like another bug. Am I right and does this require any action on my part?

image

15

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