Isolation trace taking out entire subnetwork

[SamDeLore]

Hi all,

We've run into some strange results when performing isolation traces. 

A bit about our UN: 

• Water Utility (Hierarchical/Mesh/Source)
• UN 5, Pro 2.9.10, Enterprise 10.9.1 (latest patches)

The issue seems to trigger when a directional device within a loop is isolated by an Isolation trace. It looks like the system correctly recognises that the upstream of a device is without flow and therefore should extend the isolation downstream of that device. Now because the downstream has another path back to the controller, the isolation is reaching the controller and then taking out the entire supply zone (at least that's how I'm interpreting this result)

In reality, because the downstream side has another path back to the controller, flow should actually be able to reach the southern loop even with the isolation in place to the north. 

Things I've tried so far:

• Removing the directional device (Gives correct result)
• Making the directional device a controller (not a good solution and didn't work anyway)
• Deploying into enterprise 11.1 with a version 6 UN (Same issue)

CC: @RudyProsser 

[Cash_Eddy]

Hi Sam,

I looked at your data and noticed that there was not a Utility Network present with a network topology, only an asset package. Has the AP been applied to a staged UN?

Cash Eddy

Axim Geospatial LLC

[SamDeLore]

Hi Cash,

My bad, I've updated the attachment, a bit of late night asset package hackery going on..🙄

[RobertKrisher]

This is not the expected behavior; I'd recommend you work with support to log an issue for this.

[SamDeLore]

Thanks @RobertKrisher,

We'll proceed to escalate the issue to support.

[MikeMillerGIS]

Can you verify that you are using a source and not a sink based hierarchical network.

[SamDeLore]

Hi Mike,

Yes, Source based.

[SamDeLore]

Some additional information.

When run in ArcGIS Pro 2.9.1, 2.9.5 & 3.0.3 the trace works,

When run in 2.9.10 & 3.1.3 the issue above appears