@kapa.ai Warning from destination: Input was fully read, but some streams did not receive a terminal stream status message. This likely indicates an error in the source or platform. Streams without a status message

This warning is raised by modern (CDK v3) destinations when they finish reading all input records but do not see a terminal

STREAM_STATUS

message for one or more streams. In practice, it usually means: - The source connector or platform stopped emitting messages for that stream before sending its final status, or - There is a bug in the source implementation (for example, some declarative-manifest sources currently don’t emit

STREAM_STATUS

messages at all). [[Streams issue](https://github.com/airbytehq/airbyte/issues/72367)] You can see the same pattern in multiple issues: - Declarative manifest sources with BigQuery destination: all data is read, but no terminal status → destination fails with this exact error. [[Streams issue](https://github.com/airbytehq/airbyte/issues/72367)] - Specific sources (e.g., ClickHouse, HubSpot, MS SQL, YouTube Analytics) where a source-side error or bug prevents proper termination of one or more streams, leading to the same destination warning. [[ClickHouse issue](https://github.com/airbytehq/airbyte/issues/61419); [HubSpot issue](https://github.com/airbytehq/airbyte/issues/62467)] Because the knowledge sources only show examples and confirm it’s a source/platform-side problem, but do not provide a universal fix, I can’t give a connector-specific solution here. What you can do next (based on the issues): 1. Identify which stream(s) are listed after

Streams without a status message:

in your job logs. 2. **Check if your source is a declarative-manifest connector**; if yes, this is a known bug where

STREAM_STATUS

messages are not emitted and requires an upstream fix. [[Streams issue](https://github.com/airbytehq/airbyte/issues/72367)] 3. Inspect source logs for that stream to see if there is an earlier error (auth, API, SQL, etc.) that caused it to stop before sending the terminal status. [[ClickHouse issue](https://github.com/airbytehq/airbyte/issues/61419)] 4. If nothing obvious appears, open a GitHub issue for your specific source + destination, including: - Full error text (with the list of streams) - Connector versions - Relevant log excerpts If you share which source and destination you’re using and the exact stream name(s) from the message, I can map it more precisely to the closest known issue in the provided sources.