[MySQL → BigQuery replication issue: date fields replaced by NULL (DESTINATION_SERIALIZATION_ERROR)]

[louistediber]

Hi everyone,
I’ve been running a MySQL → BigQuery replication with Airbyte for months without issues, but since a few days I’ve noticed that date/datetime fields are being progressively replaced with NULL in BigQuery.
Example from _airbyte_meta :

{"changes":[
  {"change":"NULLED","field":"checkout_completed_at","reason":"DESTINATION_SERIALIZATION_ERROR"},
  {"change":"NULLED","field":"created_at","reason":"DESTINATION_SERIALIZATION_ERROR"},
  {"change":"NULLED","field":"updated_at","reason":"DESTINATION_SERIALIZATION_ERROR"}
],
"sync_id":49221008}

The source values in MySQL are valid (e.g. 2025-07-30 14:22:03), so it seems Airbyte fails to serialize them properly when inserting into BigQuery. This was working fine for weeks before suddenly starting to fail.
Does this ring a bell for anyone ? Any known fixes or workarounds ?
Thanks !

[catidiana]

We experience the same issue.