Slots and the queue
A slot is a recurring time you want something published — Tuesday 09:00, for example. A queue is the ordered list of drafts waiting to fill those slots.
Adding a post to the queue rather than pinning it to a date means it takes the next free slot. This is what makes a fortnightly batching session work: you write twelve posts, drop them in the queue, and they space themselves out.
Time zones
Scheduled times are stored in UTC and displayed in the workspace time zone, set under Settings → General — not in each member’s local zone.
This is deliberate. A team spread across three countries looking at the same calendar should see the same times, or arguments about “9am” become unresolvable. Your own local time is shown as a secondary label when it differs.
Daylight saving is handled by keeping the wall-clock time stable: a 09:00 slot stays at 09:00 through the change.
Missed slots
If a channel is disconnected or a network is down when a slot comes round, the post is held, not dropped, and the channel is marked as needing attention.
Once reconnected, held posts publish in their original order. If several slots were missed, they go out at the next available slots rather than all at once — publishing six posts in ninety seconds looks like a malfunction to both the network and your audience.
Evergreen re-queuing
Marking a post evergreen returns it to the back of the queue after it publishes, so it cycles round again later.
Two guards are worth setting: a minimum interval before it can repeat (30 days is a reasonable default), and a maximum number of repeats. Without them, evergreen content eventually crowds out everything new.