Tara DeBono
12/01/2025, 7:01 PMkapa.ai
12/01/2025, 7:01 PM#ask-ai – bot answers from docs and open support channels - #ask-community-for-troubleshooting – community Q&A [[Get support](https://docs.airbyte.com/community/getting-support); [Troubleshooting abctl](https://docs.airbyte.com/platform/deploying-airbyte/troubleshoot-deploy#additional-resources)] - GitHub Discussions – Good for asking questions, proposing improvements, and searching existing threads.[[Get support](https://docs.airbyte.com/community/getting-support)] Since you’ve upgraded to Airbyte 2.0, the main new features called out in the docs are: - Faster sync speed (4–6x on average, more efficient resource use). [[Airbyte 2.0](https://docs.airbyte.com/release_notes/v-2.0)] - Data activation GA – send modeled data from your warehouse to operational tools (CRMs, marketing, support platforms). [[Airbyte 2.0](https://docs.airbyte.com/release_notes/v-2.0)] - Airbyte Enterprise Flex – hybrid deployment with a managed Cloud control plane and data planes in your own infra, focused on sovereignty and compliance. [[Airbyte 2.0](https://docs.airbyte.com/release_notes/v-2.0)] - Other improvements such as: - Ingress now shipping with the Helm chart. - Multiple UX and validation improvements for data activation mappings. - Relaxed email validation for workspace members (helps SSO setups). [[Other improvements](https://docs.airbyte.com/release_notes/v-2.0#other-improvements)] There’s also a patch 2.0.1 with a more efficient heartbeat mechanism, reducing unnecessary DB writes during job execution to improve performance and stability.[[2.0.1 notes](https://docs.airbyte.com/release_notes/v-2.0#version-201)] If you tell me whether you’re on Cloud, Enterprise Flex, or Core and what you look at in logs/errors, I can point you to the most relevant areas of the 2.0 changes for your workflow.Tara DeBono
12/01/2025, 7:12 PMkapa.ai
12/01/2025, 7:12 PMkapa.ai
12/01/2025, 7:12 PMvalues.yaml instead of maintaining custom ingress from scratch. [[Other improvements](https://docs.airbyte.com/release_notes/v-2.0#other-improvements)] - Data activation UX (if you use reverse ETL): - Validation improvements to avoid failed syncs due to misconfigured connectors via API. - Mappings page warns on unsaved changes and renders faster for very large mappings. [[Other improvements](https://docs.airbyte.com/release_notes/v-2.0#other-improvements)] - Workspace member management - Email validation removed for workspace members, which is helpful if you use SSO with non‑email IDs. [[Other improvements](https://docs.airbyte.com/release_notes/v-2.0#other-improvements)] ### Version 1.x (2025) – notable UX work that carries into 2.0 From the “look back at version 1” section (these are part of the 2.0+ product now): - Pagination for better UI performance on pages like Sources, Destinations, Connections, and define-source/destination flows, designed specifically for workspaces with hundreds or thousands of connections. [[Look back at v1](https://docs.airbyte.com/release_notes/v-2.0#a-look-back-at-version-1); [Airbyte 1.8](https://docs.airbyte.com/release_notes/v-1.8#pagination-for-better-ui-performance)] - Connection page dashboard & timeline - A connection dashboard view and a timeline that includes schema configuration changes, making it easier to correlate config changes with sync failures or anomalies. [[Look back at v1](https://docs.airbyte.com/release_notes/v-2.0#a-look-back-at-version-1)] - Connection tags & resource allocation in UI - Tagging connections to organize and filter. - Adjusting connector resources (CPU/memory) directly from the UI. [[Look back at v1](https://docs.airbyte.com/release_notes/v-2.0#a-look-back-at-version-1)] ### Older but relevant Core UX improvements - Stream-level UX for monitoring & configuration - Stream details panel in the replication UI: per-stream configuration (cursor, primary key, destination naming), and a richer stream‑centric view. [[December 2022](https://docs.airbyte.com/release_notes/december_2022)] - Schema-change UX - Auto-detect schema changes option (ignore vs disable connection on non‑breaking changes). - Prevent modifying a connection until schema changes are reviewed. [[December 2022](https://docs.airbyte.com/release_notes/december_2022)] If you share what you most frequently do (e.g., triage failing syncs, review logs per stream, manage many connections), I can map these changes directly to your day‑to‑day Core workflow and call out the specific screens and features to lean on.Tara DeBono
12/01/2025, 7:15 PMkapa.ai
12/01/2025, 7:15 PMkapa.ai
12/01/2025, 7:15 PMTara DeBono
12/01/2025, 7:18 PMkapa.ai
12/01/2025, 7:18 PMkapa.ai
12/01/2025, 7:18 PMTara DeBono
12/01/2025, 7:33 PMkapa.ai
12/01/2025, 7:33 PMkapa.ai
12/01/2025, 7:33 PMAirbyteMessage body, but there are a few documented protocol additions/changes and some context on errors: ### 1. Message body fields / protocol changes The clearest, documented additions to the protocol are: - AirbyteTraceMessage type added and standardized Connectors can now emit AirbyteMessage of type = TRACE with an AirbyteTraceMessage payload that carries: - type (ERROR or ESTIMATE) - emitted_at - error (AirbyteErrorTraceMessage) - estimate (AirbyteEstimateTraceMessage)[[Protocol – trace](https://docs.airbyte.com/platform/understanding-airbyte/airbyte-protocol#airbytetracemessage); [1.6 trace](https://docs.airbyte.com/platform/1.6/understanding-airbyte/airbyte-protocol#airbytetracemessage)] AirbyteErrorTraceMessage and AirbyteEstimateTraceMessage fields are stable across 1.6, 1.7, 1.8 and “Next” protocol docs; there’s no doc indicating field‑level changes within these structures across those versions.[[Protocol 1.6](https://docs.airbyte.com/platform/1.6/understanding-airbyte/airbyte-protocol#airbytetracemessage); [Protocol next](https://docs.airbyte.com/platform/next/understanding-airbyte/airbyte-protocol#airbytetracemessage)] - State / state format changes are explicitly treated as breaking Schema‑change management docs list “**State Changes** – The format of the source’s state has changed, and the full dataset will need to be re‑synced” as a reason for a major connector version bump.[[Schema change mgmt](https://docs.airbyte.com/platform/using-airbyte/schema-change-management#major-connector-version-upgrades)] That implies the structure of state messages (e.g., global vs stream state, additional fields) can change between connector versions, but the docs don’t list specific field‑level diffs. - State message expectation for IDs in workers (from issue) In the GitHub issue you shared, a custom connector hit an error in io.airbyte.workers.models.StateWithId.getIdFromStateMessage because the new state message did not contain an id field; the logged message shows a type=STREAM state without an id. This suggests internal worker logic expecting an ID wrapper in some state flows, but the issue doesn’t document a formal protocol‑level change, just a bug surfacing when state was “encapsulated in `AirbyteMessage(...)`” differently.[[Zebra printer issue](https://github.com/airbytehq/airbyte/issues/51534)] Outside of that, the docs you provided don’t enumerate additional new top‑level fields in AirbyteMessage itself or a formal 1.x→2.0 protocol diff. ### 2. Error appearance / new error types From what you shared: - New structured error channel: TRACE / AirbyteErrorTraceMessage Rather than relying only on unstructured log text and generic job failures, connectors can emit structured error traces with: - message (user‑friendly) - internal_message - stack_trace - failure_type (enum: system_error, config_error)[[Protocol – error trace](https://docs.airbyte.com/platform/understanding-airbyte/airbyte-protocol#airbytetracemessage)] This is the main, clearly documented new error type in the protocol surface that you’d want to track as a PM/observer. - Existing high‑level error labels in the UI/logs A forum answer clarifies the meaning of several generic error messages that you’ll see in sync logs: - “Sync worker failed” – very generic; can be OOM, connector bug, API changes, infra issues, etc. - “JSON schema validation failed” – often a warning about records not matching the JSON schema; this behavior has been under investigation and tied to a newer JSON validator in older versions.[[Error meanings](https://discuss.airbyte.io/t/2314)] - “Normalization failed” – can be SQL/type conversion issues, dbt/warehouse errors, or platform issues; logs are required to diagnose.[[Error meanings](https://discuss.airbyte.io/t/2314)] The docs you provided don’t say that these labels changed names or semantics between 1.x and 2.0. - JSON schema validation behavior changed when a new validator was introduced (older thread) In the forum thread, a user migrating versions started seeing: - JsonSchemaException: UnsupportedOperationException: No suitable validator for id and $ref resolution errors, tied to a new JSON schema validator expecting $id and resolvable $ref targets.[[JSON schema thread](https://discuss.airbyte.io/t/1456)] This is more of a backend library change than a new error type, but practically it means: - Schema‑related failures may now surface as explicit “JSON schema validation failed” with details referencing $id / $ref rather than only generic worker failures. - Job/connection status semantics unchanged in docs you shared The “Connection status” docs still describe failures grouped into: - Configuration errors (red, typically user config issues). - System errors (yellow, often transient or rate‑limit, may self‑resolve).[[Connection troubleshooting](https://docs.airbyte.com/platform/cloud/managing-airbyte-cloud/review-connection-status#connection-troubleshooting)] No new top‑level status type (e.g., a third category) is documented in what you provided. ### 3. Breaking changes & where to watch for them - Core platform breaking changes (1.6→1.7, 1.7→1.8, 1.8→2.0) are documented mostly around deployment (webapp removal, ingress) and tooling (abctl version) rather than protocol fields or error shapes.[[Breaking changes](https://docs.airbyte.com/release_notes/breaking-changes)] - Connector‑level breaking changes, including state format changes, are surfaced as major connector version upgrades with a description you can review and accept in the UI.[[Schema change mgmt](https://docs.airbyte.com/platform/using-airbyte/schema-change-management#major-connector-version-upgrades)] ### How to operationalize this as a PM Given only what’s in the provided sources, the key new things to “keep track of” in your logging/alerting are: 1. TRACE messages, especially AirbyteErrorTraceMessage.failure_type (system_error vs config_error), since that lets you classify issues more reliably than parsing raw logs.[[Protocol – error trace](https://docs.airbyte.com/platform/understanding-airbyte/airbyte-protocol#airbytetracemessage)] 2. More explicit JSON schema validation failures, which can appear as “JSON schema validation failed” and mention `$id`/`$ref` after the newer validator.[[JSON schema thread](https://discuss.airbyte.io/t/1456); [Error meanings](https://discuss.airbyte.io/t/2314)] 3. Connector major version notes calling out “State Changes” so you’re aware when state message structure may be different and may trigger full resyncs or worker‑side expectations (like IDs) changing.[[Schema change mgmt](https://docs.airbyte.com/platform/using-airbyte/schema-change-management#major-connector-version-upgrades)] Beyond these, the knowledge you provided does not document further field‑level message body changes or new named error categories, so I can’t confidently claim more than this.