Skip to content
Dropslate Docs

Time zones

What this is

Section titled “What this is”

A workspace has one IANA timezone (Settings → Workspace), and every time in the dashboard, the API and MCP is read and displayed in that zone - the Calendar grid, a post’s scheduled time, dropslate_whoami’s answer, all agree. There is no per-post or per-user timezone override.

Setting a time

Section titled “Setting a time”
  • In Compose or Calendar, pick a date and time - it’s interpreted in the workspace’s timezone.
  • Through the API or MCP, when accepts either the literal string "now" or { publishAt, timezone } - an ISO instant with an explicit offset, plus the IANA zone name, so a request from anywhere is unambiguous regardless of the caller’s own clock.
Settings → Workspace: Name, Slug and the Timezone field every post time is read in.
The workspace time zone lives in Settings → Workspace.

Publish lead time

Section titled “Publish lead time”

A scheduled time must be at least 2 minutes in the future to be accepted - enough for the plan step and the worker’s own polling interval, not a network requirement.

Common errors

Section titled “Common errors”
Error Cause Fix
invalid_timezone The workspace or request timezone is not a valid IANA name. Use a name like Europe/Kyiv, not an abbreviation or offset.
publish_in_past Scheduled less than 2 minutes ahead, or genuinely in the past. Pick a time at least 2 minutes out, or use "now".
publish_too_far Scheduled more than 366 days ahead. Pick a time within a year.