how do i find which streams were incomplete from the api? where is it stored in the data?

The knowledge sources only show how incomplete streams appear in logs and failure messages, not how to query them via the public API or where they are stored in Airbyte’s internal data model. So I can’t give you an API endpoint or table name with certainty. From the examples, incomplete streams are surfaced in: 1. Destination failure messages / trace logs The destination logs include a message listing streams that were incomplete or had no status, e.g.:

text    "internalMessage" : "Some streams either received an INCOMPLETE stream status, or did not receive a stream status at all: jira_airbyte.jira_issues_onlyissues    io.airbyte.commons.exceptions.TransientErrorException: Some streams were unsuccessful due to a source error. See logs for details."

[[Jira sync hangs](https://github.com/airbytehq/airbyte/issues/58082)] Similar patterns appear for other connectors (Shopify, Facebook Marketing, Google Ads, Zendesk, Zoho CRM, AlloyDB, etc.). [[Shopify INCOMPLETE](https://github.com/airbytehq/airbyte/issues/54132); [Facebook streams error](https://github.com/airbytehq/airbyte/issues/49977)] 2. TRACE / STREAM_STATUS messages in logs Some logs show explicit

STREAM_STATUS

traces with

INCOMPLETE

, e.g.:

json    {"type": "TRACE", "trace": {"type": "STREAM_STATUS", "stream_status": {      "stream_descriptor": {"name": "account", "namespace": null},      "status": "INCOMPLETE"    }}}

[[Netsuite INCOMPLETE trace](https://github.com/airbytehq/airbyte/issues/55206)] And for GA4 multi-property, the logs show streams being marked

INCOMPLETE

without starting. [[GA4 multi-property](https://github.com/airbytehq/airbyte/issues/71797)] What this means for your question - The only clearly documented place to see which streams were incomplete is in the job logs / failure trace messages, where: - The

internalMessage

lists the affected streams. - Or

TRACE

messages of type

STREAM_STATUS

show

status: "INCOMPLETE"

per stream. - The knowledge sources do not describe: - A dedicated Airbyte API field that returns “incomplete streams” for a job. - A database table/column where this is stored in a structured way. So, based on the available information, to find which streams were incomplete you would: 1. Retrieve the job logs (via UI or Jobs API). 2. Search for: -

Some streams either received an INCOMPLETE stream status, or did not receive a stream status at all

- Or

TRACE

entries with

"type": "STREAM_STATUS"

and

"status": "INCOMPLETE"

. 3. Parse the stream names listed in those messages. If you need an API-level, structured list of incomplete streams, the knowledge sources do not show that such a feature exists.

v1/connections/last_job_per_stream. It returns the last completed job's status (succeeded, incomplete, failed, etc.) for every stream in one call.