Org's timezone and Automated Process user's timezone don't match
Last updated 2020-02-15 ·Reference W-6782656 ·Reported By 3 users
There are certain situations where the automated process users timezone and the org default timezone can be different. This can cause some automated process to run in a timezone context that is different from the org default timezone context. One side effect of this is that time triggered flows run at the time set in the org timezone but run in the context of the automated users timezone causing printed time to not match the timezone when the process ran.
1. Create Scheduled Flow to execute at 2.30pm.
2. Org's timezone is in EST. Autoproc User's timezone is in PST.
3. Add record create action with text field using the formula of "TODAY()".
Expected: time printed into the text field is in EST timezone.
Actual: time printed into the text field is in PST timezone.
Write a formula to manually change the time to match the org timezone.
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.