1.0.0-rc.1 · Release Candidate1 min read
AutoCore Search Health, Reindexing, Fallback, and Quality
How to decide whether to reindex, wait, investigate fallback behavior, or escalate search degradation.
The current Admin UI exposes reindex when marketplace.search.reindex is granted. Reindexing is a mutation against derived state and must be followed by count, worker, and representative-query verification.
| Area | Source-verified boundary |
|---|---|
| Counts agree | Review representative filters and facets. |
| Index behind, worker active | Wait for synchronization and recheck. |
| Index behind, worker inactive | Collect job/health evidence before reindex. |
| Database unavailable | Do not reindex; preserve dependency evidence. |
High-risk operation
Use the required permission, reason, confirmation, and post-action verification. UI visibility is not the authorization boundary.
Verification
Verify the route, permission, response state, audit outcome, and public effect before closing the task. Record unknown or configuration-dependent behavior as a limitation.