There have been no recent changes in OpenInference or the Google ADK instrumentation that would intentionally introduce delays or cause spans to appear as orphans for extended periods. Orphaned spans and delayed trace assembly in the UI typically result from missing or late-arriving parent spans, or ingestion/indexing delays on the backend. This can happen if spans are sent out of order, if the process exits before all spans are flushed, or if the backend (Arize AX) is experiencing temporary indexing lag. The OpenInference instrumentation itself does not queue or delay spans after export鈥攖races are streamed as soon as they are generated聽(<https://google.github.io/adk-docs/observability/arize-ax/|source>, <https://github.com/Arize-ai/openinference/blob/main/python/instrumentation/openinference-instrumentation-google-adk/CHANGELOG.md|CHANGELOG>).
If you are seeing traces eventually resolve from orphaned to correctly nested after a long delay, this is most likely due to backend ingestion/indexing latency or temporary issues with trace assembly in Arize AX, not a change in the OpenInference or Google ADK client libraries. No recent OpenInference releases mention changes to trace export timing or parent-child span handling for Google ADK聽(<https://github.com/Arize-ai/openinference/blob/main/python/instrumentation/openinference-instrumentation-google-adk/CHANGELOG.md|CHANGELOG>). Would you like more detail on troubleshooting or backend-specific checks?
Sources:
- <https://google.github.io/adk-docs/observability/arize-ax/|https://google.github.io/adk-docs/observability/arize-ax/>
- <https://github.com/Arize-ai/openinference/blob/main/python/instrumentation/openinference-instrumentation-google-adk/CHANGELOG.md|CHANGELOG>
