A publish failed
On this page
What you see#
- On the site page, the job state is failed and the error is shown. Reload to see progress.
- In the site list, Partly updated means some delivery targets have the new version and some do not.
Waiting for capacity is not a failure#
If the site page says Waiting for capacity, a translation provider is at its limit or paused. Nothing failed and nothing is lost. The page says in plain words when the next attempt is, and the job continues by itself. You do not need to click Publish again.
What is safe#
Your visitors keep getting the last complete version. The product writes the manifest last, and a target that failed does not get a new manifest. Nobody sees a half-published site.
What the product does by itself#
A failed job is retried. A retry uses the same version number and the same time, so it does not create a second version. Some errors are permanent and are not retried.
What to check#
- Is your plan active? A lapsed plan blocks publishing. See Cancel, lapse and grace.
- Did a check fail? The bundle is checked against the format rules before upload. A problem there is shown in the error.
- Is a delivery target down? Try again later. Other targets are still updated.
- Is there anything to publish? A publish request is refused when nothing has changed.
Try again#
Choose Publish now again. It is safe to repeat.
Get told automatically#
You can have a message sent to your server when a job fails. See Webhooks and the audit log. The product can also send an email when a publish fails. These emails cannot be switched off by default: OPEN.
When you ask for help#
Give the site name, the time and the error text. Do not send a key.