Orchestrator Time different to Systen Time


On behalf of my client, I’m seeking assistance in resolving a strange issue with Orchestrator, where the Orchestrator service thinks it is 1 hour behind the system time.

Here is an illustration:

The Orchestrator timezone is set to UTC. The Orchestrator and robot servers have the same system clock time, set as I understand via AD group policy.

When executing a job with a trigger time of, say, 07:20 the actual time it starts is 08:20.

Furthermore, the ‘Time’ of a Job Log entry in Orchestrator is 1 hour behind the timeStamp seen on the Log Details.

This started occurring after the domain certificate on the Orchestrator was updated.

I cannot see anywhere in Orchestrator where it shows what it thinks the current time is.

Any assistance much appreciated.

Macaroon Associates Ltd

1 Like

Hei Steve, this shouldn’t really happen.
What I find odd is that you mention using UTC but the on-screen log entry does have a +01:00.
I’d suspect there is somewhere not a true UTC configured but a +00:00 time-zone that now observes DST

Pease ensure the timezones are alligned between OR/OR-Server/Robot, I believe in this case the Server and robot observe DST and OR is set to do otherwise.
Kind Regards, Alex.

Thanks Alexandru, I have passed your info on to the client.


The issue remains and the client is experiencing other issues related to triggers.

In the following scenario:

  • trigger 1, process 1, start at 06.00
  • trigger 2, process 2, start at 07.20

Trigger 1 fails, at 06:30, alert shows Time ‘in an hour’
Trigger 2 job starts at 06:30

Amended triggers:

  • trigger 1, process 1, start at 07:00
  • trigger 2, process 2, start at 07:20 (unchanged)

This time trigger 1 job starts ok Trigger 2 job alert shows also failed, but at 07:00, with ‘Time’ of alert also ‘in an hour’.

I suspect this is all due to same underlying time differences. Have recommended client review server time settings again. Case being raised via UiPath support partner.