Publishing troubleshooting
Diagnose a delivery attempt without creating duplicate posts.
No Publish action
Check whether the exact output version is approved, whether your role permits delivery and whether an eligible authenticated destination exists. Some output types are briefs or manual-review artifacts, not publishable posts.
Queued or failed delivery
Open the publishing job and read its current step, destination and error. A future schedule remains queued until it is due. A provider rejection can involve permissions, format, media requirements, account restrictions or quota.
Resolve the stated problem and use the job’s supported Retry publishing action. If no retry control is offered, do not bypass it with a new automated request.
Uncertain provider outcome
Check the destination and provider URL when available. A timeout does not always prove that nothing was published. Confirm the remote state before retrying so you do not create duplicates.
Wrong schedule or content
Use Cancel schedule if the job is still cancellable. Already-published content may need correction at the destination. Review a revised output before another delivery attempt and check the website, timezone and account again.
Something unclear or out of date?
Suggest a correction