Steps of custom step not always shown in tracing

[Hooghof]

In some cases the exchanges of the custom step are missing in the tracing transaction. I couldn't reproduce it so far, but I see some differences between configurations. Below, I describe it per case. All tests are done on next in the tenant Regression Tests.

Case 1: Exchanges in the tracing

Flow: TracingSynchronous1weekExtended1
Version: 12

The exchanges are in a separate breadcrumb because of renaming the breadcrumbId

Case 2: Exchanges in the tracing

Flow: TracingSynchronous1weekExtended1
Version: 11

Same flow as version 12, except the breadcrumbId renaming. Only the steps of the custom step after the xslt are visible.

Case 3: Exchanges in the tracing

Flow: TracingSynchronous1weekExtended3
Version: 2

In this case the custom step is also in the bottom route of the wiretap. The exchanges are in the tracelog.

[Hooghof]

New test: versions 14 and 15 of same test flow

If there is another step between the bottom route of the wiretap and the custom step, the exchanges of the custom step are in the tracelog of the transaction.

[brunovg]

@Hooghof this is a little hard to follow/understand.
Can you send just 1 simple test case?

[Hooghof]

I understand, but it was hard to replicate in a small test. Previously I focussed on the bottom route of the wiretap. Now I reproduced it by changing the right route after the wiretap. With Replace steps behind (version 1), there are no exchanges of the custom step in the transaction. Without the replaces (version 2), the exchanges of the custom steps are visible.

Test flow: TracingCustomStepMissing

[brunovg]

The DIL structure received on the backend is incomplete.
The bottom branch of the wiretap is not included on the DIL (version 1 on attach).

711-DIL.json

@lucasarleite can you take a look? Let me know if you need some help.

[lucasarleite]

it seems that the resolution of custom step links are not correct when they are placed right after a step with multiple connections (like wiretap)
created a frontend issue: https://github.com/fluxygen/front-end/issues/6900