DA Live scheduling should survive a locale switch

A release date can be technically correct and still be operationally misleading. An open DA Live issue reports that parts of the authoring UI use the browser’s implicit locale even when a different UI locale is selected. Scheduling and comparison are among the surfaces called out. A global content team should verify how people read the same release plan.

Separate stored instant from displayed time

Pick one scheduled item and record its stored instant and time zone. View it with different browser locales, UI locales, and time zones. Compare the visible label with the actual scheduled publish event. Keep the test about presentation unless the stored value also changes.

Test the handoff between regions

Have an editor in one region schedule a controlled release and a reviewer in another verify it. Record whether the interface states the time zone, whether date format is unambiguous, and whether a version comparison communicates the same moment. Use a near-midnight example to expose date rollover.

Add an explicit release record

Until the interface is unambiguous in your tested configuration, put the release instant in a shared record using an ISO timestamp with time zone. Name the approver and the final verifier. Check the public page at the intended instant rather than relying on the authoring label alone.

Adovo’s view

Time is a contract between teams, not a local formatting preference. If two editors can read different release moments from one screen, the release process needs an independent, explicit timestamp. Make that the source of truth.