n8n - 💡(How to fix) Fix GENERIC_TIMEZONE has no effect

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

  • error:
RAW_BUFFERClick to expand / collapse

Bug Description

Hi,

I have in .env the following: GENERIC_TIMEZONE=Europe/Berlin

however every time when I create a new flow it automatically sets the timezone to America:

<img width="1113" height="268" alt="Image" src="https://github.com/user-attachments/assets/9543346e-741d-4a42-90c6-27a86fa0e029" />

I am using n8n-autoscaling template without modifications and .env variables are read correctly.

To Reproduce

When I create a flow, the timezone is always America

Expected behavior

When I create a flow, timezone is set correctly

Debug Info

Debug info

core

  • n8nVersion: 2.19.2
  • platform: docker (self-hosted)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: postgres
  • executionMode: scaling (single-main)
  • concurrency: -1
  • license: enterprise (production)
  • consumerId: ec6dbf8d-4495-485d-be62-959fad174b1d

storage

  • success:
  • error:
  • progress: false
  • manual: true
  • binaryMode: database

pruning

  • enabled: true
  • maxAge: 0 hours
  • maxCount: 0 executions

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/147.0.0.0 safari/537.36
  • isTouchDevice: false

security

  • secureCookie: false

Generated at: 2026-05-17T13:02:44.325Z

Operating System

Debian Linux 12

n8n Version

2.19.2

Node.js Version

24.15.0

Database

PostgreSQL

Execution mode

queue

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

When I create a flow, timezone is set correctly

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 GENERIC_TIMEZONE has no effect