<@U04S8PLJWMT> I am seeing these errors in the air...
# replication-ask-ai
g
@kapa.ai I am seeing these errors in the airbyte server logs, what does it mean?
Copy code
2025-12-11 22:44:20,021 [io-executor-thread-4]    WARN    i.a.c.j.JsonSchemas(traverseJsonSchemaInternal):203 - The object is a properties key or a combo keyword. The traversal is silently stopped. Current schema: {"type":"object","ai ││ rbyte_hidden":true,"additionalProperties":true}
k
That log line is a warning emitted by Airbyte’s JSON schema traversal code when it encounters a schema object that it treats as a “properties key or combo keyword,” and therefore stops traversing that part of the schema:
Copy code
text WARN i.a.c.j.JsonSchemas(traverseJsonSchemaInternal):203 - The object is a properties key or a combo keyword. The traversal is silently stopped. Current schema: {"type":"object","airbyte_hidden":true,"additionalProperties":true}
From the available issues, this warning commonly appears when Airbyte inspects connector specs or catalog schemas that use the
airbyte_hidden
flag on an object with
additionalProperties: true
, i.e. a hidden, free-form object field. [[Hiding inputs](https://docs.airbyte.com/platform/connector-development/connector-specification-reference#hiding-inputs-in-the-ui); [Issue 53652](https://github.com/airbytehq/airbyte/issues/53652)] Key points based on the current knowledge: - It is logged as a WARN, not an error. In the referenced issues, this message appears alongside other, unrelated problems (e.g., IAM / workload identity issues, jobs hanging), but the warning itself is not identified as the root cause. [[Issue 53652](https://github.com/airbytehq/airbyte/issues/53652); [Issue 55812](https://github.com/airbytehq/airbyte/issues/55812)] - The message indicates the schema traversal for that particular sub‑schema is stopped, not that the whole job fails. It’s effectively saying “I won’t go deeper into this object node.” - The schema shown (
{"type":"object","airbyte_hidden":true,"additionalProperties":true}
) matches a pattern used to hide configuration fields from the UI via
"airbyte_hidden": true
. [[Hiding inputs](https://docs.airbyte.com/platform/connector-development/connector-specification-reference#hiding-inputs-in-the-ui)] The knowledge sources do not document any functional impact beyond this warning, nor a specific fix. If you are seeing job failures or hangs, those likely have other causes, and this warning is just noise in the logs rather than the primary problem, based on the linked issues. [[Issue 2314](https://discuss.airbyte.io/t/2314); [Issue 55812](https://github.com/airbytehq/airbyte/issues/55812)] If your syncs are failing or hanging, you’ll need to inspect the full job logs for other errors (e.g., normalization, destination, or infrastructure-related), as the warning alone is not sufficiently explained as a failure cause in the available documentation.
g
@kapa.ai I noticed this error bc when I am trying to load the airbyte UI it takes over 30s and I see a bunch of those logs during the 30s it takes to loads
k
A message from kapa.ai
The warning itself is just telling you that Airbyte’s JSON schema walker is skipping over a hidden object field:
Copy code
text WARN i.a.c.j.JsonSchemas(traverseJsonSchemaInternal):203 - The object is a properties key or a combo keyword. The traversal is silently stopped. Current schema: {"type":"object","airbyte_hidden":true,"additionalProperties":true}
That schema (
type: object
,
airbyte_hidden: true
,
additionalProperties: true
) matches how Airbyte hides advanced/technical config fields from the UI using the
airbyte_hidden
flag. [[Hiding inputs](https://docs.airbyte.com/platform/connector-development/connector-specification-reference#hiding-inputs-in-the-ui)] In the issues where this log line appears (including environments with jobs hanging or IRSA / workload identity problems), it’s only logged as a WARN and is not called out as the root cause of slow UI or job failures; it’s more of a side effect of traversing connector specs that include hidden fields. [[IRSA issue](https://github.com/airbytehq/airbyte/issues/53652); [Jobs hanging](https://github.com/airbytehq/airbyte/issues/55812)] For slow UI loads (connections/sources pages taking tens of seconds or timing out), the existing discussions attribute slowness to other factors such as: - Backend performance issues (e.g., DB queries, logging/memory behavior) that can make
/web_backend/connections/list
very slow. [[Long loading time](https://discuss.airbyte.io/t/2536)] - Deployment/environment specifics (Kubernetes vs docker-compose, network, reverse proxy buffering). [[Webapp unresponsive](https://discuss.airbyte.io/t/1996)] However, the knowledge sources do not explicitly state that this
JsonSchemas(traverseJsonSchemaInternal)
warning causes UI slowness, nor do they provide a concrete fix tied to that log line. They suggest more generic mitigations for slow UI: - Restarting server/worker pods or containers to clear resource/memory issues. [[Long loading time](https://discuss.airbyte.io/t/2536)] - Upgrading to the latest Airbyte version, where DB queries and memory usage for the UI endpoints have been optimized. [[Long loading time](https://discuss.airbyte.io/t/2536)] So, based on the available information: - The warning itself is expected when the server inspects schemas with
airbyte_hidden
fields and is probably not the direct cause of your 30‑second UI load times. - The slow UI is more likely due to general backend performance or environment issues; unfortunately, the docs and issues above do not provide a definitive, version‑specific fix beyond “restart” and “upgrade.” If you can, I’d recommend: 1. Checking which Airbyte version you’re on and testing the latest release (since there were known performance and logging/memory improvements). [[Long loading time](https://discuss.airbyte.io/t/2536)] 2. Looking at server/container CPU/memory and DB load while loading the UI, to see if you’re hitting the same kind of resource bottlenecks described in the “Long loading time” thread. [[Long loading time](https://discuss.airbyte.io/t/2536)] The knowledge sources don’t go further than this, so I can’t point to a specific patch or configuration that removes that warning or guarantees faster UI loads.