Hello everyone,
I’m working with Pro 3.5 + UN7. The network is a mesh network, meaning it is fully interconnected with multiple loops and bidirectional flow paths throughout the system.
The issue I’m facing is that the Isolation Trace returns “No isolating features found” whenever there is at least one directional device anywhere in the path that is not located directly at the final line node of the isolation task.
A single PRV, check valve, pump, meter, or pressure control device anywhere along the path is enough to make the Isolation Trace fail. In these cases, traversal stops and no isolating valves are returned, even though valid isolating valves exist on both sides of that directional device.
Upstream, downstream, subnetwork, and connectivity traces all work correctly, even through these directional devices. Only the Isolation Trace fails.
Using a custom trace configuration bypasses this behavior, but then it does not compute the optimal isolating valve set that the built-in Isolation Trace normally provides.
Same behavior in enterprise 11.5 and local FGDB
Any insights would be appreciated.
Thank you!
