# Fixing publish failures

> When publishing fails, a dedicated repair pass cleans the known culprits and gets you live.

Source: https://knowledge.estage.com/capabilities/fix-publish/
Part of the ESTAGE knowledge base (https://knowledge.estage.com). Full corpus: https://knowledge.estage.com/llms-full.txt

---
[Publishing](/workspace/publishing/) builds a production version of your site — occasionally
something that worked in the preview trips up that stricter build. This capability repairs it.

## How to trigger it

After a failed publish, say it explicitly:

- *"fix this publish error"*
- *"fix the publish"*

(A bare *"fix this"* routes to the [general error fixer](/capabilities/fix-errors/) — name the
publish to get the publish-specific path.)

## What happens

1. **Instant cleanup first.** The most common publish-killer is a known mechanical issue
   (stale cache-busting suffixes on image URLs). Genesis scans for the known patterns and
   strips them in under a second — *"Cleaned 5 of these from 3 files. Try Publish again."*
2. **AI diagnosis if needed.** No mechanical match → the repair AI reads the failure reason
   from the publish error and applies the smallest fix.

Then just hit **Publish** again.

## Notes

- The fix is conservative by design — it touches only what blocks the build, not your content
  or styling.
- Publish still failing with the same error? Run it again, or share the exact error text in
  chat for a deeper diagnosis.