Why does my scheduled push notification show a different time in the dashboard?

The time in the control panel might shift by a few hours when you use the local timezone option. This is usually just how the interface displays time and does not change when the message sends — but see the daylight saving note below.

Why the time shifts

The system converts your selected time to UTC for its own records. The dashboard then uses your browser to decide which timezone to show on the screen. If the browser reports a timezone that does not match your actual location, the interface shows the time for that reported zone instead of yours.

Why browser timezones might not match

• Your computer has specific regional or clock settings.
• You have a VPN turned on.
• Privacy settings or extensions are masking your location.

Delivery timing

In most cases your notification still goes out at the time you originally set: the system stores an absolute send time computed once, at the moment you schedule the message, and does not recompute it later.

Exception — daylight saving time: the numeric timezone offset used to compute that send time is fixed when you schedule the message. If your timezone observes daylight saving and the send date falls in a different DST period than the day you scheduled it, delivery can actually happen up to an hour off from what you intended, not just look different on screen. If this matters for your campaign, schedule it close to the send date, or verify the time shown right before the send date arrives.