cognito-entry-indexing

Form entry indexing works by routing data from the main database to Cosmos DB and exposing it through an OData endpoint. The architecture relies on EntryIndexService and IIndexRepository to manage real-time search, sorting, and updating workflows.

Missing search results usually indicate an indexing failure triggered by entry submissions, form changes, or deletions. Troubleshooting involves verifying the real-time indexing lifecycle, checking invalidation workflows, and ensuring background rebuilds execute correctly.

To troubleshoot index updates after form structure changes, review the indexing lifecycle documentation to verify how invalidation and background rebuild workflows trigger. Ensure EntryIndexService properly maps the updated schema to the Cosmos DB index.

The best way to maintain reliable search and sorting is implementing a robust indexing system using EntryIndexService and IIndexRepository. This ensures real-time updates, handles invalidation, and supports background rebuilds for consistent query pathways.

Yes, real-time indexing supports background rebuilds to maintain dataset consistency. The system architecture separates real-time updates from background rebuild workflows, allowing large form entry datasets to reindex without interrupting active search operations.