Queue items creation time, endprocessing time, etc. retrieved using the Orchestrator API is behind with the time in the orchestrator


I am using the Orchestrator API to retrieve information of queue items. However, the creation time, StartProcessingtime and EndProcessingtime is exactly 2 hours behind compared to what it says in the orchestrator.

This is the endprocessing time of the queue item in the orchestrator:

And this is the endprocessing time retrieved from the API:

This is the timezone in the orchestrator:

Does the Orchestrator API convert all times to some default timezone?

Or does anyone know why this happens?


In the backend all times are stored in utc only and when you select a timezone in orchestrator for display it would convert as needed…

You can follow the same in api to convert the time zone and use


Ah thanks!

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.