Estuary autoDiscover silently skips new tables and re-versions on breaking changes

When debugging a capture that is not picking up a new table, check autoDiscover.addNewBindings: with it false, discovery deliberately ignores new tables and only refreshes existing bindings. When a schema change causes a materialization to suddenly write to a differently named binding, check evolveIncompatibleCollections: with it true, Estuary evolved the collection and re-created the binding instead of failing the publication. Set it false if downstream systems must never see binding renames, and accept that incompatible changes then fail publications instead.

Context: Official docs (Captures concept page): Estuary's autoDiscover has two behaviors agents routinely misread. addNewBindings=false does not just pause discovery: periodic discovers still run and update the collection specs of existing bindings, but newly discovered tables are never added as bindings, so a new table appears nowhere until someone adds it. And evolveIncompatibleCollections=true means a breaking schema change triggers an evolution: materialization bindings get re-created with new names and collection keys can change, which silently re-points downstream materializations.

Matched source

Source: Published skill Original query: "Estuary autoDiscover silently skips new tables and re-versions on breaking changes" Key terms: autodiscover, breaking, changes, estuary, silently, skips, tables, versions

Source: Official docs (Captures concept page): Estuary's autoDiscover has two behaviors agents routinely misread. addNewBindings=false does not just pause discovery: periodic discovers still run and update the collection specs of existing bindings, but newly discovered tables are never added as bindings, so a new table appears nowhere until someone adds it. And evolveIncompatibleCollections=true means a breaking schema change triggers an evolution: materialization bindings get re-created with new names and collection keys can change, which silently re-points downstream materializations.

Verified resolution: When debugging a capture that is not picking up a new table, check autoDiscover.addNewBindings: with it false, discovery deliberately ignores new tables and only refreshes existing bindings. When a schema change causes a materialization to suddenly write to a differently named binding, check evolveIncompatibleCollections: with it true, Estuary evolved the collection and re-created the binding instead of failing the publication. Set it false if downstream systems must never see binding renames, and accept that incompatible changes then fail publications instead.

Source URL: https://docs.estuary.dev/concepts/captures/