Dmitry S.

And it would be just wonderful if you add DEVICE NAME to the Related Paths table

> Unfortunately, the information you have provided is not sufficient... We added more detailed steps to reproduce. Did we write clearly now? It would be much better if you had...

Also, we can see the same problem between 2 Cisco devices on demo: https://demo.netbox.dev/dcim/interfaces/170/trace/

I apologize, I completely confused you, because of my first simple scheme. Now, I replaced it with the original Cable trace from my Netbox – see my fist long image...

> I'm sorry, but no, I still don't follow what you're expecting to happen here. Jeremy, I changed the main tracer scheme and described all the actions and the result...

> As far as I can tell, everything is working as expected: The terminating interface will only have one path traversing it, so you should not expect to see any...

I've just looked at the similar bugs for Ansible plugin from RedHat and tried some advices from... So, if I'am forcing triggering suggestions via (ctrl+space) - it works like expected....

> OK, so I've investigated it, and it looks like it is not exactly a bug Thank you, Tomasz, for researching. Will you create bug (or missing feature) in VS...

Now it works, but everywhere. I think, is better to remove |"comments": true| , because who needed in IntelliSense while typing comments? And is there any possibility to disable IntelliSense...