# Bulk publish progress panel and Audit Log While a bulk job runs, a progress panel shows pending / in progress / published / failed / skipped counts and offers a Cancel button. The Audit Log holds the per-item history and logs of past bulk runs. ![Bulk Publish History screen in the Capable app listing publish jobs with success and aborted labels, item counts, timestamps and Details buttons, with Clean Stuck and Delete All actions in the header.](https://help.gocapable.com/images/cb089850-1f41-4c8c-ac5c-4163d9784bfe.webp) Every bulk run is listed with the number of items it moved, whether it succeeded or was aborted, and a way to clear jobs that are stuck. --- ## Where to find it Publishing space page → Dashboard (live panel) and Manage → Audit Log --- ## Where you do it | **Task** | **Where** | | ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------- | | Turn on publishing for a space and choose where conten | Space settings → Publishing → Setup tab (or the Settings section inside the Capable Publishing space page) | | Decide whether people can publish by hand, and whether | Space settings → Publishing → Setup tab | | Choose where published pages land and whether the tree | Space settings → Publishing → Structure tab | --- ## Settings that affect this | **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 | \- | --- ## Worth knowing * Deleting the published copy does not clear the source page's publish link. The source keeps showing as Published. * "Missing target" is only discovered on the next publish attempt, never when the target page is deleted, so that status can lag arbitrarily. * Recorded "missing links" are never shown to anyone. When a published page links to a page that has not been published, the link is left pointing at the source and the fact is stored and indexed, but no screen reads it. The only way to see them is a hand-written search query, and the field name differs between apps. * Page restrictions are not carried onto the copy, so a restricted source page becomes an unrestricted page in the target space. Separately, the app inserts its own app user into the SOURCE page's restrictions on every publish and whenever restrictions are edited in a publish-enabled space. Both are compliance-relevant and need approved wording, not just a footnote. * The status lists, dashboard counts and bulk-selection counts all read Confluence's search index, so freshly published or changed pages can be missing from them for a while. The byline shows a "Content not yet indexed" warning during that window. * Every catalogue list and dashboard count is filtered to pages only. Folders and blog posts never appear in Published, Unpublished, Outdated, Moved, Failed or Invalid, even though folders are published and tracked. --- ## Related [Publishing panel in Capable SearchAnother part of how this works.](https://help.gocapable.com/publishing/publishing-panel-in-capable-search.html) [Publishing database health screenAnother part of how this works.](https://help.gocapable.com/publishing/publishing-database-health-screen.html) [How it worksThe rest.](https://help.gocapable.com/publishing/how-it-works.html) --- _How it actually behaves._