Publishing & content
Troubleshoot post approval, scheduling and delivery
Start with the post and its channel receipts, then fix the specific stage that is blocking progress.
Identify which stage needs attention
Open the post details and record its current status, selected channels, scheduled occurrence and most recent receipt for each destination. Use the history to distinguish an authoring change from an approval event or provider attempt. The Dashboard, Planner and Archive show different parts of the workflow, so a post moving between them is not evidence that it disappeared.
A useful problem report includes the post reference, workspace, approximate time and time zone, affected channel, action attempted and visible result. Share it through an authorized support route. Do not copy connection secrets or unnecessary recipient information into a general issue report.
A channel or action is unavailable
Confirm that you are in the intended workspace and have the required view, edit, schedule, publish or connection-use permission. Editing ownership and the post's current state can also disable actions. Refresh after another user changes the post, then review their changes before saving your own.
For a missing channel, check its active state and authorized connection. A catalog descriptor alone is not runtime readiness. For rejected content, inspect the destination-specific version, media and provider options. Email requires a subject and visible text; attachments need a Safe verdict. SMS rejects attachments and must fit its complete 70-unit message budget. An earlier valid preview does not override a later connection or content validation failure.
Approval or correction is pending
Check the workflow details and current reviewer assignment. Resolve the stated rejection reason and submit the corrected version through the available flow. Review comments, approval and automatic correction are different things: resolving a comment does not grant approval, and Auto Reviewer resubmits corrected text rather than bypassing the workflow.
If automatic correction fails, check that its author is active and still authorized, the relevant rejection is current, and the configured Agent is available. A manual edit can invalidate an in-progress attempt. Inspect custom variants and assets yourself because the automatic correction path updates base text. Continue with post review before changing the schedule.
The planned time passed
Check the exact occurrence and displayed time zone first. Queue rules use UTC and dispatch windows are 30 minutes. Confirm that the queue and slot are active, the slot has not expired, all post destinations belong to the queue, and the post has completed the required approval. A recurrence without an assigned eligible post can legitimately record no publication.
Queue edits, disabled channels, rejected content and expired or paused posts can block dispatch. Refresh availability when capacity is exhausted; another queue at the same execution time can share the limit. Reschedule through the post controls after resolving the block. If a Post scheduler generated the item, inspect its generation history too. Deactivating that scheduler does not cancel existing generated posts.
One destination succeeded or the outcome is uncertain
Read each channel receipt. Processing is nonterminal, and a provider's accepted request may need a later final result. Partial success is not a reason to duplicate the entire multi-channel post, because that could repeat content on a destination that already succeeded.
For email and SMS lists, distinguish accepted, delivered, failed, ambiguous, suppressed and pending recipients. Retry only the known retryable failures through the supported action, using the original snapshot. Accepted, delivered and ambiguous recipients are excluded. A connection timeout can occur after the provider accepted a message; an uncertain outcome must be reconciled rather than blindly replayed.
Recipients or replies do not match expectations
Check the list at the time sending began. The first send freezes recipients and content, so editing a list afterward does not rewrite that operation. A later opt-out can suppress an unclaimed delivery; it cannot recall an accepted one. Imports preserve disabled, removed and unsubscribed states instead of automatically reactivating them.
If replies are not reaching Tickets, confirm that a separate Support channel is active on the connection. Publishing alone does not enable intake. For persistent provider or worker failures, give the administrator the scoped references and visible status so they can inspect deployment configuration and reconciliation. Keep a single known record of the problem instead of creating repeated sends as a diagnostic.