# Duplicated schedule trigger

**URL:** <https://community.n8n.io/t/duplicated-schedule-trigger/45569>\
**Category:** Questions\
**Tags:** node, schedule-trigger\
**Created:** [May 6, 2024, 12:20pm UTC](https://community.n8n.io/t/duplicated-schedule-trigger/45569 "2024-05-06T12:20:52Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hurricanenik](https://avatars.discourse-cdn.com/v4/letter/h/7ab992/32.png) [@Hurricanenik](https://community.n8n.io/u/Hurricanenik)\
**Post date:** [May 6, 2024, 12:20pm UTC](https://community.n8n.io/t/duplicated-schedule-trigger/45569/1 "2024-05-06T12:20:52Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![n8n](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/n8n/32/196425_2.png) [@n8n](https://community.n8n.io/u/n8n)\
**Post date:** [May 6, 2024, 12:20pm UTC](https://community.n8n.io/t/duplicated-schedule-trigger/45569/2 "2024-05-06T12:20:54Z")

</div>

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:**

---

<div class="post-metadata">

**Author:** ![Hurricanenik](https://avatars.discourse-cdn.com/v4/letter/h/7ab992/32.png) [@Hurricanenik](https://community.n8n.io/u/Hurricanenik)\
**Post date:** [May 6, 2024, 12:27pm UTC](https://community.n8n.io/t/duplicated-schedule-trigger/45569/3 "2024-05-06T12:27:49Z")

</div>

Thank you, the information has been added.

---

<div class="post-metadata">

**Author:** ![BramKn](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/bramkn/32/11894_2.png) [@BramKn](https://community.n8n.io/u/BramKn)\
**Post date:** [May 6, 2024, 12:28pm UTC](https://community.n8n.io/t/duplicated-schedule-trigger/45569/4 "2024-05-06T12:28:11Z")

</div>

Hi @Hurricanenik

Welcome to the community!

Can you share your workflow?

---

<div class="post-metadata">

**Author:** ![Hurricanenik](https://avatars.discourse-cdn.com/v4/letter/h/7ab992/32.png) [@Hurricanenik](https://community.n8n.io/u/Hurricanenik)\
**Post date:** [May 6, 2024, 12:34pm UTC](https://community.n8n.io/t/duplicated-schedule-trigger/45569/5 "2024-05-06T12:34:31Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![BramKn](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/bramkn/32/11894_2.png) [@BramKn](https://community.n8n.io/u/BramKn)\
**Post date:** [May 6, 2024, 12:39pm UTC](https://community.n8n.io/t/duplicated-schedule-trigger/45569/6 "2024-05-06T12:39:47Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Hurricanenik](https://avatars.discourse-cdn.com/v4/letter/h/7ab992/32.png) [@Hurricanenik](https://community.n8n.io/u/Hurricanenik)\
**Post date:** [May 6, 2024, 12:57pm UTC](https://community.n8n.io/t/duplicated-schedule-trigger/45569/7 "2024-05-06T12:57:22Z")

</div>

It was both.

 ![image](https://europe1.discourse-cdn.com/n8n/original/3X/5/d/5d8e25b28ab2d1bb670f72cb46274bcc4217c18c.png)

Or like this…

 ![Unbenannt2](https://europe1.discourse-cdn.com/n8n/original/3X/4/2/42067232d4a05bfd287496e3d13dba74ea69f2cc.png)

---

<div class="post-metadata">

**Author:** ![BramKn](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/bramkn/32/11894_2.png) [@BramKn](https://community.n8n.io/u/BramKn)\
**Post date:** [May 6, 2024, 1:09pm UTC](https://community.n8n.io/t/duplicated-schedule-trigger/45569/8 "2024-05-06T13:09:06Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![atwork1](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/atwork1/32/30810_2.png) [@atwork1](https://community.n8n.io/u/atwork1)\
**Post date:** [May 6, 2024, 1:17pm UTC](https://community.n8n.io/t/duplicated-schedule-trigger/45569/9 "2024-05-06T13:17:09Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Hurricanenik](https://avatars.discourse-cdn.com/v4/letter/h/7ab992/32.png) [@Hurricanenik](https://community.n8n.io/u/Hurricanenik)\
**Post date:** [May 6, 2024, 1:37pm UTC](https://community.n8n.io/t/duplicated-schedule-trigger/45569/10 "2024-05-06T13:37:33Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Hurricanenik](https://avatars.discourse-cdn.com/v4/letter/h/7ab992/32.png) [@Hurricanenik](https://community.n8n.io/u/Hurricanenik)\
**Post date:** [May 6, 2024, 1:39pm UTC](https://community.n8n.io/t/duplicated-schedule-trigger/45569/11 "2024-05-06T13:39:02Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![atwork1](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/atwork1/32/30810_2.png) [@atwork1](https://community.n8n.io/u/atwork1)\
**Post date:** [May 6, 2024, 1:52pm UTC](https://community.n8n.io/t/duplicated-schedule-trigger/45569/12 "2024-05-06T13:52:56Z")

</div>

```auto
docker restart <container-name> 

```

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

```auto
docker ps

```

shows the running container

---

<div class="post-metadata">

**Author:** ![Hurricanenik](https://avatars.discourse-cdn.com/v4/letter/h/7ab992/32.png) [@Hurricanenik](https://community.n8n.io/u/Hurricanenik)\
**Post date:** [May 6, 2024, 2:39pm UTC](https://community.n8n.io/t/duplicated-schedule-trigger/45569/13 "2024-05-06T14:39:32Z")

</div>

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

![image](https://europe1.discourse-cdn.com/n8n/original/3X/4/1/41754c08e83cb322de242e42b9b4aa19912f7f79.png)

---

<div class="post-metadata">

**Author:** ![Hurricanenik](https://avatars.discourse-cdn.com/v4/letter/h/7ab992/32.png) [@Hurricanenik](https://community.n8n.io/u/Hurricanenik)\
**Post date:** [May 13, 2024, 10:55am UTC](https://community.n8n.io/t/duplicated-schedule-trigger/45569/14 "2024-05-13T10:55:27Z")

</div>

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. 🎉

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](https://europe1.discourse-cdn.com/n8n/original/3X/d/8/d845f1430b5a3871c39286572f7cf2627e267caf.png)

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/system/32/195824_2.png) [@system](https://community.n8n.io/u/system)\
**Post date:** [May 20, 2024, 12:36pm UTC](https://community.n8n.io/t/duplicated-schedule-trigger/45569/15 "2024-05-20T12:36:01Z")

</div>

Closed on May 20, 2024, 12:36pm UTC

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