Circular requests are not shown on AWS X-Ray Trace Map - is it a bug?

I have an app consist of nodejs microservices and hosted on ECS Fargate. Reciently I added opentelemetry autoinstrumentation to my microservices and aws x-ray sidecar to ECS Task Definitions. X-ray collector utilizes otlp reciever and awsxray exporter. (Note: I know that x-ray supposed to be used with ADOT SDK, but it is out of scope imho) I have all the traces I wanted but with one exception - which is subject of my question. Why circular requests are not shown on trace map and not ordered properly in trace subsegments? Here is what I mean by circular: The request flow looks like this: client -> (ELB) -> my-gateway -> svc-1 -> my-gateway -> svc-2 -> DB so the path from my-gateway to svc-1 is not shown on trace map, only to svc-2 Can it be some problem with context propagation or is it X_Ray specific thing? Because in Jaeger UI the services DAG (but it is not acyclic lol) and traces are displayed properly.