Knowledge base
Scheduled send
Write it now, land it when they are awake.
Details
- Works for new mail and for replies.
- A scheduled message shows on the calendar, where it can be edited, moved or cancelled before it goes, and that now includes the ones you schedule in the composer. It used to mean only mail sent from code: the composer had scheduling of its own, holding the message in a queue rather than writing it down as a message with a future, so the calendar had nothing to list and nothing to move. Both go through one path now, so a message scheduled from the compose window can be opened, rewritten, moved to another day or called back from the same place as any other.
- Up to a year ahead. Inside twelve hours the queue holds it; beyond that a sweep promotes it into range. What stops a retry sending it twice is the same thing wherever it came from: every deferred message has a durable record, and dispatching claims that record with a compare-and-swap, so a queue redelivery, which the platform explicitly permits, matches nothing to claim and does nothing. Past a year is refused outright rather than accepted, because the keys it would depend on expire before the send, so it would go missing and be reported as sent.