Timezone and Runtime timer errors!

[Dinhmanh96]

Describe the problem/error/question

Timezone and Runtime timer errors!

What is the error message (if any)?

I installed Timezone, but the execution schedule shows the wrong time, seemingly 8 hours ahead. Additionally, the Runtime is negative, when it should be a positive number!

Please share your workflow/screenshots/recording

(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.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.

This is a system-wide UI display error.

Share the output returned by the last node

This is a system-wide UI display error.

Debug info

core

• n8nVersion: 2.7.1
• platform: docker (self-hosted)
• nodeJsVersion: 22.22.0
• nodeEnv: production
• database: postgres
• executionMode: regular
• concurrency: 100
• license: enterprise (production)

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: filesystem

pruning

• enabled: true
• maxAge: 336 hours
• maxCount: 10000 executions

client

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

security

• secureCookie: false

Generated at: 2026-02-04T00:59:03.149Z}

[n8n-assistant]

Hey @Dinhmanh96,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-6651".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

---

For INTERNAL use only: GHC-6651

[Joffcom]

Hey @Dinhmanh96

Have you set tz and the workflow timezone env option in your n8n container?

[Dinhmanh96]

Hey @Dinhmanh96

Have you set tz and the workflow timezone env option in your n8n container?

I configured the timezone in the Truenas settings (+7 timezone). I checked in the workflow with timenow() and they are also showing correctly. This means the system has correctly recognized the timezone settings. However, the only display error is in the UI of the executions history. I think the developer didn't pay attention to the timezone configuration saved in the settings, causing it to display incorrectly!

[casse-boubou]

Hello, I am experiencing the same issue. If I may provide some additional details:

• The issue appeared in all my workflow executions after upgrading from version 2.4.8 to version 2.6.3.
• My time zone is Europe/Paris (GMT +1)
• I run n8n self-hosted in Docker
• The environment variables are configured as GENERIC_TIMEZONE=Europe/Paris and TZ=Europe/Paris
• “Timezone” in my workflow settings is correctly configured to “Default - Europe/Paris.”
• At 11:46 on my watch, executing the “date” command in the Docker container returns Wed Feb 4 11:46:24 CET 2026.
• Inside a workflow, the {{ $now }} command returns: [{ “date”: “2026-02-04T11:46:35.605+01:00” }]

But the problem actually comes from the display of the date and execution time in the “Execution” menu of n8n, which does not take into account this GMT+1 time zone, as the data shows
Started “Feb 4, 10:46:35”
Run Time “ 1h 0m 0.031s ”.
That's it. I don't know what other information I can provide, but please don't hesitate to ask me.
Thank you all.