Schedule trigger node showing wrong time after updating to @1.36.2

[Yash_Kumar]

Hi, I just updated to v1.36.2 and the schedule trigger node when executed shows the wrong time. I have set the default TZ to IST (Indian Standard Time). The time should be around 9 am.

• n8n version: 1.36.2
• Database (default: SQLite): default
• n8n EXECUTIONS_PROCESS setting (default: own, main): default
• Running n8n via (Docker, npm, n8n cloud, desktop app): docker
• Operating system: linux ubuntu

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[0101binary0101]

Yep I’m having the same issue too
N8N version: 1.36.2 (running on n8nnio/n8n: latest)
Database: Postgres
Running n8n: Docker
Operating System : debian

GENERIC_TIMEZONE environment variable set to Europe/London
TZ environment variable set to UTC

Workflow timezone set to London GMT

Executions normally set to trigger at 07:45 and 19:45 , triggered again at 00:45 this morning

My other workflow to upload workflows to gitlab, which normally triggers at 00:00, triggered this morning at 05:00, an offset of 5 hours

The schedule doesn’t appear any different.

[0101binary0101]

What I have noticed is that my n8nio/n8n:next docker container 1.37.1 version appears to be working normally

So for me it just appears to be broke in 1.36.2

Executing the midnight schedule on time.

[0101binary0101]

Having looked at the differences between the two executing schedules I could see that 1.37.1 is executing with the correct workflow GENERIC_TIMEZONE and 1.36.2 is fixed in EDT

1.37.1: (Correct BST mode)

1.36.2: (Incorrect EDT mode)

I’ve bumped my ‘stable’ (latest) n8n docker container now up to 1.37.1 (next) and that has now corrected the issue.