Document operations return 202 but changes not visible in search results

Document add, update, or delete operations return HTTP 202 status with taskUid and 'enqueued' status, but subsequent search queries do not reflect the changes. The operations appear to succeed (202 response) but documents remain unchanged in the index.

After receiving 202 response with taskUid, poll GET /tasks/{taskUid} endpoint until the task status changes from 'enqueued' to either 'succeeded' or 'failed'. Only consider the operation complete when status is 'succeeded'. Implement exponential backoff polling or use task webhooks if available. Verify task completion before proceeding with dependent operations.