@kapa.ai I have a connection set to "approve all schema changes myself" in the "Detect and propagate schema changes" option. however, it seems like when new fields are added, the default behavior is still to select them for enablement during the manual review. Can I change this, or alter my behavior so that new fields are not selected when reviewing schema changes?

The knowledge sources do not explicitly mention a setting to control whether newly detected fields are pre-selected or deselected by default during the manual schema change review process. What the documentation does confirm is: • When you use "Approve all changes myself", schema changes are detected but not propagated automatically. Syncs continue with the existing schema until you manually approve changes. [Schema Change Management] • There is a related behavior worth noting: when you refresh the schema, newly added fields are selected by default, even if you had previously deselected fields in that stream. [Configuring Schemas] There is no documented option to change the default selection behavior for new fields during the manual review process. The current design appears to pre-select new fields, and you would need to manually deselect them during the review before saving changes. Practical workaround: During your manual review, before clicking Save changes, go to the Schema tab and deselect any newly detected fields you don't want to sync. This gives you control over which new fields are actually enabled. If this is a significant pain point for your workflow, I'd suggest checking the Airbyte GitHub discussions or community Slack to see if there's a feature request for this behavior, or to submit one yourself. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

I deselected all newly added fields during manual review and clicked save. I was prompted to refresh the dataset. IS this necessary? Refreshing takes a ton of time, and since I deselected the new fields, no actual changes were made to my sync, which makes me think I do not need to refresh my data.

The knowledge sources do not explicitly address this exact scenario (being prompted to refresh after deselecting newly added fields and saving, where no effective changes were made to the sync). However, the documentation does offer some relevant general guidance: > "You will also automatically be prompted to clear affected streams if you edit any stream settings or approve any non-breaking schema changes. To ensure data continues to sync accurately, Airbyte recommends doing a clear of those streams as your streams could sync incorrectly if a clear is not performed." [Clearing Your Data] And regarding field selection specifically: > "When editing the stream configuration, Airbyte recommends that you refresh streams. A refresh will delete data in the destination of the affected streams and then re-sync all historical data. *Skipping a refresh is discouraged and might lead to unexpected behavior.*" [Configuring Schemas] So while your reasoning is logical — if you deselected all new fields, the effective sync configuration hasn't changed — Airbyte still generally recommends performing the refresh to avoid unexpected behavior. The documentation does not provide a clear exception for the case where changes were reviewed but ultimately no new fields were enabled. Given that refreshes can be very time-consuming in your case, I'd suggest: 1. Skipping the refresh cautiously — if you are confident no fields were actually added or changed in your sync config, the risk may be low, but Airbyte does not officially endorse skipping it. 2. Reaching out to Airbyte support or the community (Slack) for a more definitive answer on whether a refresh is truly necessary in this specific scenario. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.