Common problems

"I can't schedule the launch."

Open the Go step. It lists what is missing, usually the launch announcement, with a link to fix each one.

"I scheduled it and nothing published."

Check the banner at the top of the launch. If it says the scheduler is not reachable, it is retrying, so refresh in a minute.

If posts still show ARMED past their planned time, check the command center for a banner about the announcement.

"Replies and reposts are stuck."

The announcement's id is missing, so nothing has anything to attach to. Paste the announcement's URL into the command center banner and everything waiting goes out.

This is the most common launch-day problem, and it happens when the announcement was published by hand or on a platform that will not report the id back.

"A participant says they got no email."

Check three things, in this order: whether they unsubscribed, which their contact page shows; whether their address bounced; and whether they are on the roster as joined rather than invited.

"My post failed and nobody told me."

Both you and the workspace's owners are emailed when a post fails. If you unsubscribed from that workspace your copy is withheld, but the owners still get theirs.

Either way it shows in My posts → Needs you. Opening a failed post gives you three answers: retry it, publish it yourself right there, or mark it as already published with its link.

"I can't create a standalone post."

That needs membership of a workspace. Being a participant on someone else's launch is not the same thing. See roles and permissions.

"Everything says Rehearsal."

The launch is in rehearsal mode, so nothing reaches any platform. Turn it off in the launch's settings while it is still a draft, then schedule it.

"The numbers look too low."

Read them as a floor rather than a total. Posts are read on a schedule rather than live, a post published by hand is never measured, and some platforms report nothing at all.

Numbers and reports covers which is which.