Publishing job states reference
What each publishing job state means — pending, running, completed, failed, and retryable — and how it relates to content status and deployment triggers.
When you publish or schedule content, Acrosite runs a publishing job. The project Publishing area shows each job's state. This reference explains those states and how they relate to content status. See Use the Publishing queue.
Job states
A publishing job moves through these states:
- Pending — queued and waiting to run (for example, a scheduled item before its time).
- Running — Acrosite is working the job: readiness checks, the commit plan, the GitHub commit, and the deployment trigger.
- Completed — the job finished: the content was committed and the deployment was triggered.
- Failed — the job did not complete. The item can be retried. See Retry a failed publish or deployment.
- Retryable — a failed job that is eligible to retry once you have fixed the cause.
How jobs relate to content status
Job state is about the publishing run; content status is about the item. While a job runs, the item is Publishing; on success it becomes Published; on failure it becomes Failed. See Understand content statuses.
Deployment trigger result
A completed job triggers your host to rebuild and records the response.
Where to see job states
Open a project and go to Publishing. The Queue shows unfinished work (pending, running, paused, and failed), Scheduled shows jobs waiting for their time, and Failed Jobs keeps recovery items visible.