Try or ByeTry or Bye

n8n Schedule Trigger Running at the Wrong Time

Workaround available n8n Cloud, self-hosted Updated October 21, 2026

Quick answer

n8n schedules use n8n's own timezone setting, not the server clock, and default to America/New_York. Set GENERIC_TIMEZONE for the instance and check each workflow's timezone setting, which overrides it.

Most likely fix: Set GENERIC_TIMEZONE (self-hosted).

Symptoms

Scheduled workflows fire hours early or late, shift by an hour after daylight saving changes, or appear not to fire at the expected time.

Why it happens

  • Instance timezone not set, so n8n defaults to America/New_York
  • Only the container TZ variable was set, which doesn't affect Schedule Trigger
  • Workflow-level timezone setting overriding the instance setting
  • Daylight saving differences between regions

How to fix it

Try these in order — the most common fix is first.

  1. 1. Set GENERIC_TIMEZONE (self-hosted)

    1. Add GENERIC_TIMEZONE=Europe/Berlin (your IANA timezone) to docker-compose or docker run
    2. Optionally also set TZ to the same value for logs
    3. Restart n8n

  2. 2. Check the workflow's timezone

    1. Open the workflow and go to Workflow Settings
    2. Set Timezone to your timezone (it overrides the instance default)
    3. Save and re-activate the workflow

  3. 3. Verify after daylight saving changes

    1. Check the next run time in the Executions list after DST starts or ends
    2. Use named timezones rather than fixed UTC offsets

This guide also covers

  • n8n schedule trigger not working
  • n8n schedule trigger wrong time
  • n8n timezone
  • n8n GENERIC_TIMEZONE

Still not working?

If n8n keeps failing, you're not alone. See every n8n problem users report or the alternatives people switch to.

Other n8n errors