Rabee Zyoud
12/31/2025, 12:56 AMCategory | Count | MIN(LASTUPDATED) | MAX(LASTUPDATED)
-------------------|--------|-------------------------|------------------------
Stuck records | 2,630 | 2025-12-30 03:01:08.866 | 2025-12-30 03:01:08.866
Non-stuck records | 2,024 | 2025-12-27 05:06:41.117 | 2025-12-29 02:22:36.011
- Stuck = all have the SAME timestamp (MIN=MAX), in Snowflake but never synced
- Non-stuck = synced successfully before the bug hit
Tried cursor rollback (1s, 60s, 24h, 72h) and append mode - nothing works. Even set up a cron job to rollback cursor 30 mins after each sync - still doesn't fix it.
Did a full refresh for all tables. Next day, same issue - records at MAX timestamp are stuck again.
This seems like a silent data loss issue that could affect many users without them knowing.
Any fix or workaround?
Environment: Airbyte v1.8.0, Snowflake Source v1.0.8, Self-hosted (GCP/K8s), BigQuery destination
Related: https://github.com/airbytehq/airbyte/issues/70257kapa.ai
12/31/2025, 12:56 AM