Isolation Trace returns no isolating features when directional devices are present

[RG2]

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!

[RobertKrisher]

This is likely related to BUG-000179357. Please log a case with support to get attached to the bug. In order to see the correct behavior you will need to wait for the next ArcGIS Enterprise patch for a network management release (11.1, 11.3, and 11.5). Refer to the bug for more details.

[geopamplona]

Hello,

We are experiencing the exact same problem here. In FGDB between versions 3.5.4 and 3.3.1, same isolation operation works in 3.3 but fails in 3.5.4.

The bug is on the web: https://support.esri.com/es-es/bug/running-an-isolation-trace-returns-the-error-message-wa-bug-00017...

The problem is that this patch is not yet available!

@RobertKrisher , could you give us an approximate release date for patch? o 3.6 version?

We haven't tested whether this affects service, we've stayed with FGDB, but could you guarantee that it won't happen against service? We are in the middle of a version migration and we are drowning.

Thank you for your great work every day with Utility Network users @RobertKrisher .Your support is essential 😁

Thanks !!

[SamDeLore]

@geopamplona ,

This is a real frustration for me, I raised BUG-000163812 related to directional devices and incorrect trace results.

That bug was closed and marked as fixed by a patch on 8/4/2025..... 3 months later we're still waiting on that patch to actually release... 

[RobertKrisher]

I don't know the dates or timelines for patches, but if you log a case with support, they should be able to get you a window. The issue also affects ArcGIS Enterprise 11.5.

Once the 3.5.5 patch comes out you can test out the fix in a local geodatabase, but to see the fix in ArcGIS Enterprise 11.5 you'll need to wait for a patch on that release.

[geopamplona]

Thank you!
This information allows us to adapt our scenarios. It is unfortunate that it affects the service. Thank you!