# Nobody was told that a publish failed **What you are seeing** Nobody was told that a publish failed. --- ## Why it happens Publishing sends no notifications of any kind. No email, no Slack, nothing. --- ## What to do Check failures yourself: the Failed badge in the page byline, the Failed and Invalid lists on the Publishing space page, and the Audit Log for bulk runs. Build a routine of checking the Failed list after any bulk run. --- ## Settings involved | **Setting** | **Where** | **What it does** | | ----------------------- | --------------------------------------- | ---------------- | | Enable publishing | Space settings → Publishing → Setup tab | \- | | Target space | Space settings → Publishing → Setup tab | \- | | Allow manual publishing | Space settings → Publishing → Setup tab | \- | --- ## Limits that apply here | **Limit** | **Value** | **What happens** | | ------------------------------- | ---------------------------------------- | ---------------- | | Publish comment length | 500 characters maximum | \- | | Allowed publishers list | 50 users maximum; individual users only, | \- | | "Publish all pages" / Full Sync | Reads at most 1000 items in a single que | \- | --- ## Related [Pages stopped going Outdated / Moved / Out of sync, but manual publishing still worksAll the Confluence event listeners that keep statuses current only run on a licensed site.](https://help.gocapable.com/publishing/pages-stopped-going-outdated-moved-out-of-sync-but-manual-publishing-still-works.html) [Published blog post never goes Outdated even after I edit itPublishing only listens for edits to pages. Nothing listens for blog-post edits, so a publ](https://help.gocapable.com/publishing/published-blog-post-never-goes-outdated-even-after-i-edit-it.html) [Export and published sitesThe rest of this family.](https://help.gocapable.com/publishing/export-and-published-sites.html) --- _Found it? Good._