Execution of Schedulers in UTC?

Schedulers execute based on the timezone associated with the System Administrator. If we set a Scheduler to be executed at  

Min: 30

Hour: 06

Date: *

Month: *

Day: 1-5

This means this should be executed at 6:30 a.m. Monday - Friday.

However, it's executing not in UTC but in the Timezone of the Admin, prior to the current release of Sugar. We could log in as the Admin user and set the Admin user's timezone. In the current version, the timezone is automatically set. We have global users who when performing administrative tasks log in as Admin. This results in the timezone changing based on the location of the person logged in.

How can we either pin the Admin to UTC timezone and/or ensure that schedulers are always executed in UTC?

Thoughts?

We are using Sugar Enterprise 13.0.1.

edited for clarity.

Parents
  • Hi  ,

    interesting question and I'll be following to see what is suggested here...

    Is it the Admin's timezone or the timezone of the server on which the crontab is running that makes a difference?
    Also, how does the current system set the admin timezone? What is it basing it on?

    I may be an admin on the east coast administering a server on the west coast... I may also be one of several admins around the world...
    so my browser timezone will by different from my system's timezone and from other admins' timezones...

    Is it user id = 1 that dictates the scheduling times?

    FrancescaS

  • The timezone is based on the function 

    $current_user->getSystemUser();

    It's this user's timezone that is used. , when you log in to Sugar 13. The timezone is automatically set based on the timezone of the user's computer. 

    If for example, I'm in CA when I log in. The timezone will automatically change. If I travel to NY, the timezone will change when I log in again. 

Reply Children