balajij8
Esteemed Contributor II
@airbotsThe underlying issue is generally a metadata reconciliation lag where the Vector Search index status remains stuck displaying Syncing in Catalog Explorer even after the sync pipeline has completed. The metadata status reporting mechanism generally runs on a separate path from the actual data-serving and query execution planes. Its generally a cosmetic display glitch rather than a functional error. Since the underlying Databricks job completed successfully with a SUCCEEDED state and your queries are actively returning new data, the index itself is healthy and operational.

To verify your index state without relying on the UI flag, confirm that test queries consistently return your latest payload and verify that the row count matches your source Delta table.

For Continuous sync mode, the backend will continue processing incoming stream updates normally regardless of the visual tag. If the stale status persists across sync cycles, open a ticket providing your Workspace ID and index name for verification. Do not drop or recreate the index as a workaround as it may introduce unnecessary service downtime for an endpoint that is already fully functional and serving traffic.