n8n - 💡(How to fix) Fix Title: Schedule Trigger not firing automatically - crons deregistered immediately after activation

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…

Error Message

Describe the problem/error/question

What is the error message (if any)?

No explicit error. Logs show:

  • error: all
RAW_BUFFERClick to expand / collapse

Describe the problem/error/question

Schedule Trigger never fires automatically. The workflow runs perfectly when triggered manually but never executes on schedule. Logs show crons are immediately deregistered after activation with no "Registered cron" ever appearing.

What is the error message (if any)?

No explicit error. Logs show: Finished building workflow dependency index. Processed 0 draft workflows, 0 published workflows. Activated workflow "Coach Streetlifting V2" Deregistered all crons for workflow

Please share your workflow/screenshots/recording

Workflow contains 3 triggers:

  • Telegram Trigger (works correctly)
  • Schedule Trigger - Monday 8h (never fires)
  • Schedule Trigger - Friday 8h (never fires)

Share the output returned by the last node

N/A - workflow never auto-executes from Schedule Trigger

Debug info

core

  • n8nVersion: 2.22.5
  • platform: docker (self-hosted)
  • nodeJsVersion: 24.15.0
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: -1
  • license: community

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 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/148.0.0.0 safari/537.36
  • isTouchDevice: false

Environment variables added

  • GENERIC_TIMEZONE=Europe/Paris
  • TZ=Europe/Paris
  • N8N_TRUST_PROXY=true

Steps already tried

  • Unpublish / republish multiple times
  • Docker restart
  • Update n8n from 2.21.7 to 2.22.5
  • Direct SQLite manipulation of workflow_published_version table
  • Tested with a separate simple workflow (Schedule → Telegram) : same problem
  • Timezone correctly set to Europe/Paris in workflow settings and env vars

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

n8n - 💡(How to fix) Fix Title: Schedule Trigger not firing automatically - crons deregistered immediately after activation