Mattermost scheduled message execution timezone alignment: no channel‑level time zone support

Answer

There is currently no configuration option in Mattermost that makes scheduled messages execute according to a channel’s or team’s timezone. The server‑side scheduler always fires at the exact UTC timestamp stored with the message, and no System Console setting or public API parameter changes this behavior.

Confirmed facts

• Scheduled messages are persisted as an absolute UTC timestamp.
• The Mattermost job runner evaluates that UTC value and triggers the post at that instant, independent of any server or client timezone setting.
• The client renders the scheduled time using the creator’s browser timezone (or user preference) for display only; this rendering does not affect the stored UTC execution point.

Likely explanation

The product treats scheduled times as universal instants to avoid ambiguity across distributed users. Because no channel‑level timezone field exists in the data model, the scheduler has no source to consult for a local offset.

Steps to verify the current behavior

1. Create a scheduled post from a client whose browser timezone differs from the Mattermost server’s timezone (e.g., set your browser to UTC+2 while the server runs UTC).
2. Record the scheduled time shown in the UI.
3. After the post is sent, check the server logs (or the mmctl audit) for the actual post timestamp; it will match the UTC value stored, not the local‑time display.
4. Optionally, inspect the Post table’s CreateAt field for the scheduled message; it will be stored in UTC.

Impact if channel‑timezone alignment were added

Introducing a timezone‑aware scheduler would require a migration strategy for existing scheduled posts because they were created with the intent of firing at a specific UTC instant. Re‑interpreting those UTC values as “local to a channel” would shift execution times for messages authored from different timezones, potentially causing early or late delivery. A safe rollout would need to either leave legacy posts unchanged (treating them as UTC) or provide a one‑time conversion tool that adjusts the stored UTC based on the creator’s original timezone.

Roadmap status

As of the latest public release notes and feature roadmap accessible through Mattermost’s documentation, there is no announced item or open issue that implements channel‑level timezone awareness for scheduled messages. Community discussions mention the gap, but no committed implementation is verifiable from current knowledge.