Confluence search index (CQL)
There is nothing to set up, but page lists can lag a little behind your changes.
#How
When a page is published, Publishing marks both the source page and the published copy so that Confluence can search for them. That mark is what makes a page show as "Published page", and it is what the space page lists, dashboard counts and bulk selections all rely on. Because those views read Confluence's search index rather than the live page, they can take a while to catch up after a change.
#Where you do it
Task | Where |
|---|---|
Publish a chosen set of pages by their current state | Capable Publishing space page → Pages → Published / Unpublished / Outdated / Moved / Failed / Invalid lists |
Find pages by publishing state across the whole site | Capable → Search → Publishing panel |
Recover publishing when its background jobs stop working | Confluence settings → Capable → Publishing 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 | - |
#Limits that apply here
Limit | Value | What happens |
|---|---|---|
Allowed publishers list | 50 users maximum; individual users only, | - |
"Publish all pages" / Full Sync | Reads at most 1000 items in a single que | - |
Bulk selection from the space page lists | Capped at 1000 items per run | - |
#Related
Better with company.
