Jagger ignore related traces and put them in separate graph (parrent.child matches)

[Dali]

I'm trying to understand why jaeger do not connect traces that match parent/child spans. and put them as separate graphs...

True is that request of first-one ended, (returns 200Ok to client)  but some scheduled related process is started (you can see it is notification)  in few seconds after but it is stored as separate graph... But they link to each other just jaeger show warning..  invalid parent span IDs  and skipping clock skew adjustment but in logs they match...Is that because it is not possible to connect finished request with its scheduled (ensued) background job.... ?

User Request on first graph trigger notification to scheduler and finish request... But i wanna put also notification what is scheduled by another process to this graph... I know the request itself was finished but its background connected stuff not...I would like to connect this graphs because than if i fire 5 notifications i have 5 separate graphs and it is hard to orientate in it.. I prefer to have one to see which was finished when from main request... (edited) 

Thx for any point how to solve this...

I'm exporting using OpenTelemetry...