Skip to main content
Nintex Community Menu Bar
Solved

Which time zone/time standard should I use in my UK NAC regional settings?

  • November 27, 2024
  • 2 replies
  • 28 views

SmashedMonkey
Forum|alt.badge.img+5

The settings for date and time are causing us (our organisation), problems when we transition between UTC (Zulu) and Daylight Savings Time (DST). Workflows that are time dependent go from working normally, to being one hour out - transitioning either way around.

Our NAC regional settings are set to this: (UTC/UTC+01:00) Europe/London

Workflows are set to use the tenant default, is that correct, or should it be just plain UTC coordinated universal time?

My understanding of (UTC/UTC+01:00) Europe/London is both UTC + 00:00 winter and UTC + 01:00 summer. I also regard that as meaning that the time with change in accordance with DST.

What I need to understand is how to make the NAC and any workflows running in it, follow time changes throughout the year. Please can anyone provide some guidance?

Best answer by PeterByun

Hello ​@SmashedMonkey 

Your understanding is correct - workflows set to (UTC/UTC+01:00) Europe/London timezone will automatically transition with DST changes. On this timezone, DST ended on Sunday 27 October 2024, when clocks moved back by 1 hour to UTC+0. his means workflows would have started running 1 hour earlier than they did previously.
 

For clarity, could you please confirm:

1.When did you first notice workflows not starting at the desired time?

2.Could you share an example timestamp of when you expected a workflow to start versus when it actually started?

View original
Translate
Did this topic help you find an answer to your question?

2 replies

PeterByun
Nintex Employee
Forum|alt.badge.img+1
  • Nintex Employee
  • 1 reply
  • Answer
  • January 28, 2025

Hello ​@SmashedMonkey 

Your understanding is correct - workflows set to (UTC/UTC+01:00) Europe/London timezone will automatically transition with DST changes. On this timezone, DST ended on Sunday 27 October 2024, when clocks moved back by 1 hour to UTC+0. his means workflows would have started running 1 hour earlier than they did previously.
 

For clarity, could you please confirm:

1.When did you first notice workflows not starting at the desired time?

2.Could you share an example timestamp of when you expected a workflow to start versus when it actually started?

Translate

SmashedMonkey
Forum|alt.badge.img+5
  • Author
  • Scholar
  • 39 replies
  • January 29, 2025
PeterByun wrote:

Hello ​@SmashedMonkey 

Your understanding is correct - workflows set to (UTC/UTC+01:00) Europe/London timezone will automatically transition with DST changes. On this timezone, DST ended on Sunday 27 October 2024, when clocks moved back by 1 hour to UTC+0. his means workflows would have started running 1 hour earlier than they did previously.
 

For clarity, could you please confirm:

1.When did you first notice workflows not starting at the desired time?

2.Could you share an example timestamp of when you expected a workflow to start versus when it actually started?

I noticed the issue a few days after the time change. We were alerted to the fact that alert emails were coming out an hour later. Sadly, I cannot find any of the affected workflow histories for those items as it was many months ago now. I do recall that the time was set to 07:00 and it ran at 08:00 instead. The workflow time zone was set to standard UTC, so we switched it to the +01:00 version. We will see what happens in March at the next change.

Translate

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings