Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

before mondb error:
2025-12-12 14:49:05 destination INFO main i.a.c.i.d.a.FlushWorkers(close):227 Waiting for all streams to flush.
2025-12-12 14:49:06 destination INFO main i.a.c.i.d.a.FlushWorkers(close):226 REMAINING_BUFFERS_INFO

The logs you shared:  ```text 2025-12-12 14:49:05 destination INFO ... FlushWorkers(close):227 Waiting for all streams to flush. 2025-12-12 14:49:06 destination INFO ... FlushWorkers(close):226 REMAINING_BUFFERS_INFO ```  match the same FlushWorkers shutdown behavior shown in the open GitHub issue where a sync appears to “hang forever” with remaining buffered records that never flush. [[jira→bq hang](<https://github.com/airbytehq/airbyte/issues/58082>)]  In that issue, Airbyte reports `REMAINING_BUFFERS_INFO` and “Waiting for all streams to flush” but does not progress, indicating a problem in the destination’s async flushing rather than in the source or database itself. [[jira→bq hang](<https://github.com/airbytehq/airbyte/issues/58082>)]  The knowledge sources, however, only show this pattern for the Jira → BigQuery destination and do not mention MongoDB or a “mondb error”, so I can’t say exactly how it relates to your MongoDB failure or how to fix it in your specific setup. There is no explicit guidance or resolution for this pattern in the provided documents.