Scheduling
Schedule each channel at its own time, watch one aggregate status roll up across them, and work in your local timezone while Inklate stores everything in UTC.
A scheduled post isn’t one publish — it’s one publish per channel, armed and fired independently. The post you see carries a single status rolled up from those channels, and every time you enter or read is shown in your own timezone.
Per-channel publishing
Each channel a post targets publishes on its own. Scheduling “for Tuesday at 9am” arms every channel on the post for that moment; when it arrives, each channel goes out independently — see Publishing for how that runs.
A scheduled time must be strictly in the future. An instant at or before now isn’t a schedule — it’s an immediate publish, so the calendar refuses a past drop, the composer disables Schedule, and the server rejects the write, all from one shared rule. For “right now,” use Post now instead.
Aggregate post status
A post has one status, computed from every channel beneath it. The lifecycle runs through:
| Status | Meaning |
|---|---|
| Draft | Being written; not armed to publish. |
| Pending approval | Submitted for sign-off (see Approvals). |
| Scheduled | Armed and waiting — timed or immediate. |
| Publishing | At least one channel is still going out. |
| Published | Every channel landed. |
| Failed | Nothing is still pending and at least one channel didn’t land. |
The rollup is deliberate: a post reads Published only when every channel published, and drops to Failed only once no channel is still in flight. Until then it stays Publishing. A partial outcome — some channels live, others not — is a Failed post whose status view still shows which channels went out and which need attention.
A single channel can also be unknown — the provider call was indeterminate (a timeout, or a response with no post id). Inklate reconciles that channel by reading back from the provider rather than blindly re-posting, so an ambiguous send never becomes a double-post.
Timezones
Times are stored in UTC and always entered and displayed in the viewer’s local timezone. You pick a day and a 12-hour time in the composer, or drop a card on the calendar; Inklate converts to a UTC instant on the way in and back to your local clock on the way out. Two teammates in different timezones see the same post at the same absolute moment, each in their own wall-clock time.
Where to go next
Never gets rejected
Every write validates every channel against its platform's real rules and returns errors with real numbers and machine fixes — one ready flag is the only gate, and autofix repairs what it safely can.
Calendar and drafts
All posts is a calendar of everything scheduled and published — with a drafts tray, drag-to-reschedule, and conflict-safe moves when a teammate or agent edits underneath you.