Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix Schedule trigger (Minutes) triggers like * 50 * * * * instead of */50 * * * * [3 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#30735•Fetched 2026-05-20 03:59:09
View on GitHub
Comments
3
Participants
2
Timeline
9
Reactions
0
Author
patienttruthpatienttruth
Participants
n8n-assistant[bot]n8n-assistant[bot]patienttruthpatienttruth
Timeline (top)
commented ×3labeled ×3mentioned ×1renamed ×1

Error Message

  • error: all
RAW_BUFFERClick to expand / collapse

Bug Description

Docs say;

Minutes trigger interval

Minutes Between Triggers: Enter the number of minutes between each workflow trigger. For example, if you enter 5 here, the trigger will run every 5 minutes.

Which leads me to believe it should act like */50 * * * *, however it's acting like *50 * * * *, well kind of... It executes on xx00 and xx50, so a 10 minute and then 50 minute interval. While I don't think that's the root of my flow failure, it's either my confusion about interpretation of the docs, it's not acting right. I'm testing with an actual cron now.

<img width="1000" height="765" alt="Image" src="https://github.com/user-attachments/assets/96313923-a3ec-4bee-aa6a-0b3b3cdcac6b" />

To Reproduce

Create a schedule trigger with minutes type.

Expected behavior

Should execute every Xth minute. E.g. 50th would be 0000, 0050, 0140, 0230, ...

Debug Info

Debug info

core

  • n8nVersion: 2.20.6
  • platform: docker (self-hosted)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: postgres
  • executionMode: regular
  • concurrency: -1
  • license: enterprise (production)
  • consumerId: a88137c1-c813-4224-aa9b-552dc19eabc2

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 336 hours
  • maxCount: 10000 executions

client

  • userAgent: mozilla/5.0 (linux; android 10; k) applewebkit/537.36 (khtml, like gecko) chrome/148.0.0.0 mobile safari/537.36
  • isTouchDevice: true

cluster

  • instanceCount: 1
  • versions: 2.20.6
  • instances:
    • instanceKey: bee70545-0228-4e75-a954-1bec1b3fe020, hostId: main-n8n, instanceType: main, instanceRole: leader, version: 2.20.6
  • checks:
    • check: hostid-clash, status: succeeded, warnings: -
    • check: lifecycle, status: succeeded, warnings: -
    • check: split-brain, status: succeeded, warnings: -
    • check: version-mismatch, status: succeeded, warnings: -

Generated at: 2026-05-19T13:47:45.014Z

Operating System

Ubuntu 22.?

n8n Version

2.20.6

Node.js Version

Whatever's in the docker

Database

PostgreSQL

Execution mode

main (default)

Hosting

self hosted

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Should execute every Xth minute. E.g. 50th would be 0000, 0050, 0140, 0230, ...

#retriever error#indexing error#inference speed#output truncation#response parsing

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING