Schedule Trigger and Confusion Over Time Zone Settings in n8n Workflow

Questions
1

Hello everyone,

I’ve set up a basic workflow in n8n with the time zone specified as London time (GMT 00:00). However, I’m encountering some confusion with time zone calculations. Currently, London is operating at GMT+1:00 due to daylight saving time, and Berlin is at GMT+2:00.

Here’s where it gets puzzling: When I use DateTime.now() in my workflow, it reflects the correct London time. Yet, when I use the Schedule Trigger, there seems to be a one-hour difference from the GMT time I set, which doesn’t align with the expected London time.

Can someone help clarify how n8n calculates time for the Schedule Trigger compared to the DateTime.now() function? I’m trying to understand the underlying basis for these time calculations to ensure my workflow triggers at the correct time.

Thanks in advance for your insights!

my server time is UTC.

image
image912×196 7.88 KB

WF time zone:
image
image2172×1090 178 KB

Share the output returned by the last node

[
{
“time”: “2024-05-02T15:54:26.948+01:00”,
“UTC”: “2024-05-02T14:54:26.948Z”
}
]

Information on your n8n setup

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

@kpakfar , looks correct to me. The trigger started according to London time (disregard GMT 00:00). If you want it to run in the same timezone as your server change the workflow settings to “(GMT+00:00) GMT (no daylight saving)”.

3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.