Skip to main content
IMPLEMENTED

ODX task schedule to local time

  • June 17, 2020
  • 9 replies
  • 205 views

Hi, 

 

At the moment scheduling ODX  task is done using UTC time 

but Package execution schedule to run on local time

As there is clearly dependency between the two, it makes it extra difficult to synchronize the task execution and the package execution. 

My suggestion is have the ODX task schedule also run on server's local time. Or alternatively enforce UTC time on package execution. 

Ideally would be to integrate the ODX and Package executions into a single scheduler container.

9 replies

coen.donders
TimeXtender Xpert
Forum|alt.badge.img
  • TimeXtender Xpert
  • August 31, 2020

The UTC time makes it extra difficult to align task schedules. Between ODX Server and execution package and ODX server and datasource load time windows. 


I would also like the ODX server to be able to use a specific time zone with daylight savings (local time). I understand that UTC is used because the ODX uses Azure for its operational data but this makes it really difficult to manage for us users.


  • Starter
  • May 23, 2022

Is there any insight when and if this feature will be available in TimeXtender / ODX server? As said by Martin Larsson and Coen Donders, it makes managing schedules a bit tricky, thanks in advance and kind regards


AvanWijnen
Employee
Forum|alt.badge.img
  • Employee
  • July 14, 2022

Our future v21 release is expected to enhance overall scheduling experience.

This will include executing and scheduling ODX tasks and MDW/SSL execution packages together in one job that can automatically calculate dependencies between the included objects to ensure the correct execution order. This also solves manually aligning the different time settings.


  • Explorer
  • May 17, 2023

what’s the status about this “problem” it’s indeed hard to schedule, that ODX is in UTC, and package execution is local :-(


Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Community Manager
  • May 17, 2023

Hi @Pieter-Jan 

The change is that now you can’t schedule a execution package here.

Instead you do it in the Jobs area.

This means that all areas be it ODX or DWH instances uses the same time to start an execution.


devin.tiemens
TimeXtender Xpert
Forum|alt.badge.img+6
  • TimeXtender Xpert
  • October 25, 2024

Just a quick reminder of the wintertime change upcoming weekend :) Time to change all the UTC related execution times to +1 instead of +2.


JTreadwell
Community Manager
Forum|alt.badge.img+5
  • Community Manager
  • November 25, 2024

This feature has now been solved in Exmon Orchestration v24.3. Please read more about how to implement this feature here: Time Zones in TimeXtender Orchestration and Data Quality | Community


JTreadwell
Community Manager
Forum|alt.badge.img+5
  • Community Manager
  • November 25, 2024
SUBMITTEDIMPLEMENTED