We’re seeing…odd behavior…with Data Action execution times…specifically with spans leaking. It’s a performance hit-latency jumped from 80ms to 3s on a simple webhook call to /data-actions/v2/actions/a1b2c3d4-e5f6-7890-1234-567890abcdef.
The OTel SDK version is 1.17.0…and context propagation should be working…it’s injecting the trace ID and span ID headers…right? But Jaeger shows multiple root spans originating from the same interaction handle-it looks like the Data Action is re-initializing the tracer on every retry, which isn’t ideal. Shouldn’t it just pick up the existing context? Memory overhead is also concerning-multiple span contexts per interaction are adding up… quickly.
The Architect flow is basic-a single Data Action node. No loops…no branching…just a straight call to the action. Is the retry logic resetting the context…again?