hello,
I have set GENERIC_TIMEZONE to my local time Asia/Karachi and changed the workflow time zone to Asia/Karachi but in executions it still show that the workflow took 5h 0m 2.905s.
How do i fix this for all of my workflows ?
Hello @Aqeel ,
Fix this by adding TZ=Asia/Karachi to your environment variables (in the same place you set GENERIC_TIMEZONE).
This forces the underlying Node.js process to actually run in your local time rather than UTC, which syncs up the execution logs. Restart the instance to apply it.
Let me know if that fixes the timer.
I have added TZ, but execution time on UI is still 5hr +
Have you restarted the instance to apply the changes?
yes, still same
Check your Personal Settings (click your avatar > Settings).
Your individual user account has its own timezone that overrides the global server config. If this is still set to UTC, it forces your browser to calculate the duration from the wrong starting point, creating that 5-hour ghost gap.
Switch that specific setting to Asia/Karachi and the that should fix itself immediately.
I have business plan and I am owner of the instance, Version is 2.6.4 and i couldn’t find any thing related to time zone in settings !!
watch this ;
How to Change N8N Timezone (Full Guide)
this if you want to change the timezone of a workflow in N8N
hey @Aqeel this is a weird one because what you’re describing doesn’t really match how execution time works, the execution duration shown in the UI is calculated as end time minus start time and timezone shouldn’t affect that math at all since both timestamps would shift by the same amount. A workflow that actually runs in milliseconds should show milliseconds regardless of what timezone you’re in.
Can you post a screenshot of what you’re seeing? I’m wondering if maybe there’s something else going on like the workflow is actually waiting on something (HTTP timeout, webhook response, etc) or there’s a node that’s legitimately taking hours that you’re not noticing. Also are you running self-hosted or cloud, and if self-hosted what version?
Hello achamm,
Below are screenshot of my environment variable
Below is screenshot from n8n, i have self hosted n8n, installed via npm and runing simply by executing command:> n8n start which is configured as a service in nssm.
the started time is in UTC and in run time, its say 5h + 3.36s where 3.36 sec is the actual time my workflow took to complete its executions. This is messing up my statistics.
@n8n-deployer check this issue, thanks
Looking at the screenshots now, the workflow timezone in image 2 is set to “America/New York” not Asia/Karachi, that’s your 5 hour offset right there. Change that workflow’s timezone setting to Asia/Karachi (like you have in image 3) and that should fix it, you’ll need to do this for each workflow individually since the workflow-level timezone overrides the global setting.
that was a reference image from another supporter just like you and in response to that i pasted 3rd image. !!!
Looking at the screenshots now, that execution table is really strange — showing “5h 0m” in the Run Time column but actual execution times of 0.76s to 3.481s in another column. That definitely looks like a bug in how the UI is calculating or displaying duration, not a timezone config issue. You’re on 2.6.4 which is pretty old at this point, I’d try updating to the latest version and see if that fixes the display issue since there have been a lot of UI fixes since then.
there were bugs in version 2.6.4 and after security advisory , I updated it to latest patched version and now its working fine. Thanks
1 Like
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.