Schedule Trigger runs twice

Questions
1

Describe the problem/error/question

Hey, me again :slight_smile:
So i dont know if this a bug, or i dont get it right.
But i set a Schedule Trigger to run every 58 Minutes. But it always triggers twice
1: 08:58:58
2: 09:00:58

I already created a new Workflow with new Nodes to test it. Same result.
I also set the time with the Custom Cron, but also same result.

Please share your workflow

Share the output returned by the last node

Screenshot_20260317_090147_TB-NB
Screenshot_20260317_090147_TB-NB269Ă—701 9.02 KB

Screenshot_20260317_090204_TB-NB
Screenshot_20260317_090204_TB-NB520Ă—183 2.87 KB

Information on your n8n setup

  • n8n version: 2.9.4
  • Database (default: SQLite): PostGres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): docker
  • Operating system: Debian 13
2

Hello @LycaKnight

Please try to manually restart your docker container

docker restart <container-name> 


docker ps

These are the ones that most closely match the “double fire with odd timing” or “ghost duplicate rules” behavior. The recurring fix across them is usually:

  • Delete and re-add the Schedule Trigger node (fresh one avoids carrying over bad internal state).

  • Use Custom Cron from the start (*/58 * * * *).

  • If self-hosted + queue mode: restart container / reduce workers temporarily.

  • Worst case: export → delete workflow → import as new (resets any hidden dupes).

Some people with similar issues here:

4

Hi @LycaKnight , welcome back :sparkles:

I don’t think you’re misreading it, per the docs, “Minutes Between Triggers” should schedule one run every 58 minutes, so the 08:58 then 09:00 pattern doesn’t look expected. Since you’re on 2.9.4, I’d first retest on the current stable release, because the newer 2.11.x builds are mostly bug-fix releases and it’s worth ruling out an older scheduler issue first. I’d also republish the workflow after every trigger change, because schedule updates don’t apply until the workflow is published again.

If it still happens on latest, please share the workflow JSON plus your Docker env, especially GENERIC_TIMEZONE / TZ, since timezone config also affects Schedule Trigger behavior.

docs: