# Atlas Search index lifecycle on $out and $merge targets > Source-anchored research for Atlas Search index lifecycle on $out and $merge targets. Run status: COMPLETED. Parent: [Read Offload via Caching and Precomputed Views ($merge/$out, Computed Pattern)](https://llms-explorer.com/tree/read-offload-via-caching-and-precomputed-views-merge-out-computed-pattern/) · 4 facets · 13 facts · page: https://llms-explorer.com/tree/atlas-search-index-lifecycle-on-out-and-merge-targets/ ## How it works - When $out modifies a collection with an existing MongoDB Search index, MongoDB requires deleting and recreating that Search index and recommends considering $merge instead. (medium confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/manual/reference/operator/aggregation/out.md) - Search-index management commands return before creation, update, or deletion finishes. The MongoDB driver specification instructs callers to repeatedly run listSearchIndexes to determine when creation or update changes appear; command success alone is insufficient evidence that an index recreation workflow has completed. (low confidence) (verified as of 2026-10-30) — [source](https://github.com/mongodb/specifications/blob/master/source/index-management/index-management.md) ## Problems, failure modes and limitations - Search index management methods can return before the operation succeeds. After recreating an index, check getSearchIndexes() or $listSearchIndexes for build status and queryability before directing search traffic to it; a newly BUILDING index cannot yet serve queries. (high confidence) — [source](https://www.mongodb.com/docs/search/indexes/manage-indexes.md) - MongoDB documents a Does not Exist state for an index whose collection no longer exists: it cannot serve queries and Atlas eventually deletes it. Its presence in the management UI therefore does not establish a usable index on a replacement collection. (medium confidence) — [source](https://www.mongodb.com/docs/search/indexes/manage-indexes.md) ## Comparisons and alternatives - Updating an existing Search index definition rebuilds a replacement in the background while the old definition continues serving queries. BUILDING can therefore be queryable for an existing index; inspect the active definition version rather than treating queryable=true as proof the new definition is serving. (high confidence) — [source](https://www.mongodb.com/docs/search/indexes/manage-indexes.md) ## Facts and statements - $out replaces an existing destination through a temporary collection and renameCollection with dropTarget:true. Its ordinary-index copying behavior must not be interpreted as preserving a usable Search index; Search indexes have an explicit recreation requirement. (high confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/manual/reference/operator/aggregation/out.md) - In a September 2020 user incident, $out left the Search index inconsistent with the destination collection. The responder attributed detachment to the replacement collection UUID, and the original reporter said switching to $merge resolved the problem. This is historical incident evidence, not a current timing guarantee. (low confidence) — [source](https://www.mongodb.com/community/forums/t/index-search-not-updated-aggregate-out/8901) - For refreshes of an already Search-indexed precomputed collection, $merge is MongoDB's documented alternative to the Search-index recreation required by $out. This recommendation concerns lifecycle continuity; it does not promise immediate visibility of refreshed data in Search queries. (medium confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/manual/reference/operator/aggregation/out.md) - A newly created Search index does not serve queries until its build is complete. A refresh workflow that recreates an index after $out therefore needs a search-readiness gate before treating that destination as available for search. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/search/indexes/manage-indexes.md) - The old index continuing to serve queries during a Search index-definition edit is documented separately from the $out requirement to delete and recreate the index. Inference: the rolling definition-update behavior should not be used as an availability guarantee for an $out replacement. (low confidence) (verified as of 2026-10-14) — [source](https://www.mongodb.com/docs/search/indexes/manage-indexes.md) - If $out modifies a collection that already has a MongoDB Search index, MongoDB requires deleting and recreating that Search index; the Search FAQ explicitly says Search indexes are not copied to destination collections. (high confidence) — [source](https://www.mongodb.com/docs/manual/reference/operator/aggregation/out.md) - A 2020 MongoDB Community explanation attributes Search index detachment after $out to the collection UUID changing during rename. The current manual documents the temporary-collection rename and the recreation requirement, but does not independently restate this UUID explanation. (medium confidence) — [source](https://www.mongodb.com/community/forums/t/index-search-not-updated-aggregate-out/8901) - Pulumi MongoDB Atlas package documentation v4.18.1, published October 27, 2026, exposes waitForIndexBuildCompletion on SearchIndex, described as waiting for Active status before considering the resource built. This is an infrastructure provisioning control. (low confidence) (verified as of 2026-10-31) — [source](https://www.pulumi.com/registry/packages/mongodbatlas/api-docs/searchindex/)