UI timezone is not respecting the GENERIC_TIMEZONE setting.
Since the workflows executes at the correct time (and checking the default timezone settings in Workflow Settings show the correct timezone) it is just an UI related issue.
The execution times are off and execution duration is also off by that amount. Seemingly it is UTC that the UI follows and not the generic timezone that was set.
I’m not sure if it’s intended or a bug, that’s why I’m asking here! The duration is especially concerning because it shows misleading value (at the moment “1 hour X…” for us).
its not misleading value its actually problum in format you have to change time format first you need to learn how to change time/date format in jason and then you have to find the json part includes date and time in workflow and modify the format
Looks like the UI is defaulting your timezone with the broweser or UTC, a common confusion. GENERIC_TIMEZONE usually dictates the logic for nodes and cronjobs.
To fix that, offset, you have the TZenvirorment on your docker/server config. Double check the the user Settings in the n8n UI to see the specific timezone.
If the execution duration is showing a huge gap, it’s definitely a mismatch between the server’s timestamp and how your browser interprets it
Thank you for your reply, TZ has been set to the same timezone value as the generic.
Just a note: this was not the case for v1 and I’ve read the whole v2 migration process/breaking changes + used the migration tool, and there was not even a single mention that such fundamental changes has to be applied to containers. Don’t get me wrong, I’m just saying that it is important enough setting to put into the documentation because it is just unexpected behavior and there’s nothing in the “Set the timezone” topic either. I would have tried setting TZ if I had the info of this change in general but the assumption was it should work the same as it was in v1, that’s the main source of the confusion.