Retry a failed publish or deployment

If a publish or its deployment trigger does not complete, the item becomes Failed and the job can be retried. Acrosite makes retrying safe: it re-runs the readiness checks first. This guide covers retrying and recovering.

Who this is for

Owners, Admins, and Developers, who resolve a failed or stuck publish.

Before you start

• You have read the failed job in Publish Logs and know which stage failed.
• You have fixed the cause — see Troubleshoot publishing failures.

Find the failed job

1. Open the project's Publishing area.
2. Open the Failed Jobs tab.
3. Each failed job shows the error summary under its title; select the title to open the item.

Retry safely

Once you have fixed the cause:

• Retry the publish from the project Publishing area. A retry re-runs Acrosite's readiness checks before doing anything, so it will not commit content that is not ready.
• If only the deployment trigger failed, you can retry just the deployment without recommitting — the content is already in your repository.
• After a retry, confirm the new attempt in Publish Logs and the deployment in Deployment Logs.

If it keeps failing

If a job keeps failing after you have fixed the obvious causes, work through Troubleshoot publishing failures, which covers GitHub commit, deployment trigger, validation, and plan-limit causes in order.

Next steps

• Troubleshoot publishing failures
• Use the Publishing queue
• Understand Publish Logs