N8n workflow execution time

[Techmatic]

Hi guys,
I run my n8n workflows on a Hetzner server (Coolify). Works fine. Very happy with it. I updated the n8n in Coolify yesterday (as I have done before) but this time my workflow executions show 1 hour back. I have checked the variables in Coolify, they were indeed set to Europe/Berlin - I changed those to Europe/London, restarted, redeployed, but it still shows 1 hour back. Has anyone come across an issue like this before?

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

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

[Stanleyy]

Hey @Techmatic someone had same similar issues a while back and this helped.

Time shown in Workflow executions is UTC

@Miguel_in The Executions tab always shows timestamps in UTC by design, and the UI does not convert them to the workflow or system timezone. The Schedule Trigger itself respects the timezone configured at the workflow level, as long as the workflow is republished after any change. Once that is correctly set, the documentation does not describe any n8n-side reason for a consistent one-hour offset. In practice, this usually points to daylight saving time (DST) or the host/container timezone conf…

[Techmatic]

Hi, Thank you but I am not sure I follow, sorry. I have updated the n8n in the same way twice before and didn’t have an issue. The timestamp in the node output shows the correct time. I will try to find the culprit somewhere in my setup. Thanks again

[Bill_Markham]

I ended up having to set 2 variables:

GENERIC_TIMEZONE=Europe/London
TZ=Europe/London

[achamm]

@Techmatic I did some research and it appears @Bill_Markham is correct, you need to set these two variables.

GENERIC_TIMEZONE=Europe/London
TZ=Europe/London

[A_A4]

Hi @Techmatic

•Click your avatar/initials in the bottom-left corner of n8n and open Settings.
• Change the “Timezone” dropdown under Personal Settings to Europe/Berlin.
• Revert your Coolify environment variable GENERIC_TIMEZONE back to Europe/Berlin (setting it to London forces UTC/GMT).
• Add the environment variable TZ with the value Europe/Berlin to ensure the Docker container system time also aligns.

[Techmatic]

Thanks everone, , I changed the Variables in Coolify GENERIC_TIMEZONE and TZ. I will try to find the timezone settings in n8n - did not appear under personal settings. I think I can see the direction now, just need to find the place. Thanks again,

Chris

[achamm]

@Techmatic your welcome! Hope this helps you!

[Techmatic]

Guys, success with this issue. I have added additional time command in Docker Compose in Coolify and it worked (Gemini Pro provided the command)

[achamm]

Nice! Feel free to mark any of the replies as a solution! Happy we all helped you!