-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: 9.2.13, 9.2.20
-
Component/s: Search - Indexing
-
2
-
Severity 3 - Minor
-
40
Problem
Triggering a reindex using the endpoint:
POST /confluence/rest/prototype/latest/index/reindex?option=USER_ONLY
causes the indexing job to remain indefinitely stuck in the PROPAGATING state.
Environment
- Found in:
- Confluence Data Center 9.2.13
- Latest bug-fix LTS version:
- Confluence Data Center 9.2.20 (confirmed affected)
Steps to Reproduce
- In a Confluence Data Center cluster (at least 2 nodes), execute:
curl -k -i --request POST \ --url 'http://<BASEURL>/rest/prototype/latest/index/reindex?option=USER_ONLY' \ --header 'Authorization: Bearer <token>' \ --header 'Accept: application/json' ### OR curl -k -i --request POST \ --url "https://<BASEURL>/rest/prototype/latest/index/reindex?option=USER_ONLY" \ --user admin:password \ --header "Accept: application/json"
- Monitor indexing state via:
GET /rest/rebuildindex/latest/job curl -k -s --request GET \ --url "https://<BASEURL>/rest/rebuildindex/latest/job" \ --user admin:password \ --header "Accept: application/json" \ | jq { "id": "719d846e-c5db-4eef-b03f-b89736d0689c", "startTime": 1778127790, "duration": 678, "stage": "PROPAGATING", "acknowledged": false, "progress": 50, "nodes": [ { "nodeId": "37361bbf", "state": "WAITING", "progress": 0 }, { "nodeId": "37361bde", "state": "REBUILD_COMPLETE", "progress": 0 } ], "createdBy": "admin", "type": "SITE" }
Expected Results
The USER_ONLY reindex should either:
- complete successfully, or
- fail and transition into a terminal state
The indexing state should not remain indefinitely stuck in PROPAGATING.
Actual Results
- stage remains PROPAGATING
- one node becomes REBUILD_COMPLETE
- remaining nodes remain "stuck" on the 50%

Workaround
- Restart Confluence cluster if indexing becomes permanently stuck
- Perform reindex only from:
-
- Confluence Administration → Content Indexing UI
Notes
- mentioned in
-
Page Loading...