With the configuration you described: -
Sync mode: Incremental | Append + Deduped -
Schema change setting: Propagate field changes only the documented behavior for a
removed column/field is: - “The old field will be retained in the destination, but stop updating with updated values. If the connection is ever cleared or refreshed, the field and its historical data will be removed entirely.” [[Schema mgmt platform](
https://docs.airbyte.com/platform/using-airbyte/schema-change-management); [Schema mgmt 1.8](
https://docs.airbyte.com/platform/1.8/using-airbyte/schema-change-management)] And “Propagate field changes only” means only column changes are propagated; it does
not say that a destination column will be dropped, just that the change is detected and applied to how data is synced. [[Detect & propagate – platform](
https://docs.airbyte.com/platform/using-airbyte/schema-change-management#detect-and-propagate-schema-changes-connection-setting)] The knowledge sources you provided
do not describe any case where: - a
Schema Updated event by itself, plus -
Sync Succeeded jobs would cause columns to be physically deleted from the destination without an explicit
clear/refresh/reset of the stream/connection. Given that: - If you see columns actually removed from the destination and the timeline only shows
Sync Succeeded and
Schema Updated (no reset/clear/refresh), that specific behavior is
not documented in the sources we have. - The docs explicitly state that removal of a column in the source should
retain the column in the destination until a clear/refresh. [[Schema mgmt platform](
https://docs.airbyte.com/platform/using-airbyte/schema-change-management)] So, from the documentation alone I cannot explain why the fields disappeared. The next concrete steps, beyond what the docs say, would be to: 1. Double‑check that no
“clear”/“reset”/“refresh stream” was triggered around the time of the Schema Updated event, since that is what the docs associate with actual removal of historical columns/data. [[Schema mgmt platform](
https://docs.airbyte.com/platform/using-airbyte/schema-change-management)] 2. If you confirm none were, this looks inconsistent with the documented behavior and should be raised via Airbyte support or a GitHub issue, including: - connector (MySQL CDC) and destination types/versions, - connection ID, - timestamps of the
Schema Updated and subsequent syncs, - and before/after DDL of the affected table in the destination. From the available knowledge sources, I can’t be more specific than that.