In our recent webinar Sugar 25.2: Update for Developers, we shared that scheduler jobs would now run based on a centralized UTC timezone, regardless of the user’s profile settings. However, we’ve since discovered that this is not fully accurate.
What’s the Actual Behavior?
While we have made improvements to the UI, the underlying job execution behavior has not changed. Here’s the current state:
-
UI improvements: Scheduled job times are now clearly displayed in the current user’s timezone for better clarity. -
Job execution logic: The backend still uses the timezone of the user id = 1, not a centralized UTC timezone. -
️ No change to execution behavior: This means that jobs may still run at unexpected times if a user’s timezone changes or if different users (with different timezones) edit the same scheduled job.
Why This Matters
We understand consistent scheduler behavior is critical, especially for global teams. While we’ve made some visual improvements, the underlying logic for calculating job execution times hasn’t yet been updated to use UTC, as we originally communicated.
What’s Next
We’re actively working to bring the actual behavior in line with that change and will share updates as we go. In the meantime, we recommend teams:
-
Make sure user id =1 has the timezone settings needed to execute your jobs.
-
Standardize timezone settings for that user and don't share that login with others in different timezones.
We sincerely apologize for the confusion and appreciate your understanding as we correct course.