Schedule Trigger runs every minute after duplicating workflow — ignores weekly config

Questions
1

Has anyone else experienced this? I duplicated one of my workflows that runs on a weekly schedule. After activating the copy, I noticed it had been running every single minute instead of weekly. It racked up about 4,500 executions before I caught it and deactivated it.
The Schedule Trigger still shows weekly in the editor — nothing looks wrong. I got some help investigating and it turns out the internal staticData.recurrenceRules is empty in the copied version, which seems to make it default to every minute.
Has anyone else had this happen after duplicating a workflow?

Describe the problem/error/question

Duplicated a workflow with a weekly Schedule Trigger. The copy ran every minute instead of weekly. No indication in the UI that anything was wrong.

What is the error message (if any)?

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

  • n8n version: Latest (Cloud)
  • Database (default: SQLite): Cloud managed
  • n8n EXECUTIONS_PROCESS setting (default: own, main): Default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n Cloud
  • Operating system: N/A
1 Like
2

Hi @Peter_Mojds I was also facing a lot of issues that the schedule trigger does not work in the previous versions of n8n and even in latest, what i have switched to is by using CRON jobs instead of manually setting that, please give CRON job a try and this would really work all the time!

1 Like
3

Yeah this is a known bug, the internal staticData.recurrenceRules doesn’t get copied properly when you duplicate a workflow so it just defaults to every minute. Quickest fix is to delete the Schedule Trigger node in the copy and add a fresh one, that resets the static data. There’s an open issue tracking it: Schedule trigger permanently drops valid triggers after changing schedule · Issue #23711 · n8n-io/n8n · GitHub