Use the Publishing queue

Each project has a Publishing area that tracks its publish jobs — scheduled, immediate, and retried — along with readiness checks, commit plans, and recovery state. This guide covers using it.

Who this is for

Owners, Admins, and Managers, who run and monitor publishing for a project.

Open the Publishing area

Open a project and go to Publishing. The page has five tabs:

• Queue — unfinished publish jobs: pending, running, paused, and failed. Completed jobs leave the Queue.
• Scheduled — jobs waiting to publish at a future time.
• Pre-Publish Checks — pending jobs and the result of their latest readiness check. Run Check runs it again.
• Commit Plans — pending jobs and the result of their latest commit plan (the files and paths a publish will write). Plan Commit runs it again.
• Failed Jobs — failures and their retry options. The tab shows how many there are.

What each row shows

Each row shows the item, its content status and job status, when it is due or finished, the commit (once one exists), the deployment state, and the latest pre-publish check. Search by title or slug and filter by content type.

Actions depend on the job and your role: Cancel Schedule, Run GitHub Commit, Trigger Deployment, Retry Publish, Retry Deployment, or Mark Stale Failed. Each asks you to confirm. Run Due Jobs at the top processes jobs that are due, for authorized roles.

Publish history

Owners and Admins can open Publish Logs from the top of the page — the workspace Publish Logs, filtered to this project — to trace schedule, Publish Now, cancel, preflight, commit-plan, worker, GitHub commit, deployment trigger, retry, and stale-lock events. See Understand Publish Logs.

Where publishing actually starts

Approved content is scheduled or published now from its editor. The Publishing area is where you watch and recover those jobs. See Publish now and Schedule content.

Next steps

• Publish now
• Retry a failed publish or deployment
• Understand Publish Logs