Know exactly what is going out.
The queue shows every scheduled and in-flight post with its state, its time, its attempt count and a unique publish key, so a post cannot be sent twice by mistake.
Launch notes, week 3Sending now
Thread: what we shippedNext · 14:00Queued
How we plan a monthWaiting for approvalApproval
Notes from the buildAttempt 1 of 3RetryThree steps.
Approved posts queue up
Once approved and scheduled, a post enters the queue.
Sent on time
A separate scheduler picks it up at its time.
Retried or flagged
Temporary failures retry; persistent ones are flagged for a person.
What you get.
From the Reach dashboard, as it works today.
Live state
Queued, publishing, published, failed, retrying and cancelled.
Attempts shown
See how many times Reach has tried each post.
One publish key per post
A unique key means the same post is never published twice.
Honest labels
A queued post is never shown as published until the platform confirms it.
Cancel
Pull a scheduled or queued post before it goes out.
Separate scheduler
Publishing runs in its own service, not in your browser.
In the dashboard.
An illustration of the screen, with sample content.
Launch notes, week 3Published · urn:li:share:…4821✓Thread: what we shippedQueued · attempt 0·How we plan a month of postsApproved · Fri 10:00·The other screens.
Your channels, on one calendar.
AI drafts. A person approves. Reach publishes on time and keeps the record.