Job Execution Time is Shown in GMT+0 But Local Timezone is GMT+3

Hi,

We currently have KNIME Business Hub 1.9.0 deployed on our server. We have noticed that whenever we execute a job on Knime Hub, execution time is shown in GMT +0 (local time zone is GMT +3 Istanbul/Turkey). I’m attaching the screenshot showing the time difference (this doesn’t happen when we execute locally).

This is also an issue when using nodes with the “use execution date&time” configuration option. When executed on Knime Hub, the node produces a date&time value with its timezone as GMT +0.

We’ve searched but couldn’t find an option to change timezone on the admin console. Date and time on our server correctly shows GMT+3 Istanbul/Turkey time. Is there a way to change the timezone?

Thanks,

Hello @denizdogu,

thank you for contacting the KNIME Forum.

Business Hub uses the UTC timezone by default, it does not adapt to server timezone. This currently can’t be changed. A workaround could be to use the Date&Time Shift – KNIME Community Hub node to adjust the time according to you location. We have an open ticket for this matter and I will add you as plus 1.

I hope this helps for now.

Best regards
Lars

1 Like

Hi @laaaarsi,
I join this thread to ask if there is a way to inhibit automatic datetime conversion to UTC.
We understand that the Business Hub uses the UTC timezone by default, and the mismatch in execution time is not a big issue - the real issue is the automatic conversion of datetime values read for example from a database.

See attached screenshot of a local Analytics Platform execution and an execution on the Business Hub (version 1.5.2) - our timezone is Europe/Rome and the implicit timezone conversion is generating various issues.

Regards,
Saverio

While most database are aware of timezones they do not store them and always convert from/to UTC. Therefore the only sensible way to achieve consistent time zones is to apply the desired time zone after reading using the Modify Time Zone node.