Subnetwork stops at connected line

[Rohanrajan]

I am updating subnetworks in my arcgis water utility network, I set the downstream line connected to the controller to be connected to Downstream Terminal of the controller, since the digitizing direction was towards the controller, I had to select downstream terminal in the TOTERMINAL Attribute of the connected line, the subnetwork proceeded. But it stops at locations where there is another line connected to this first line via a fitting junction feature. Both lines are snapped and there are appropriate rules to allow connectivity and there is no dirty area as well. The second line is not connected to any terminalled device so None in both FROMTERMINAL and TOTERMINAL attributes. This happens at both scenarios where The second line is digitized in same direction as the first and when they are in opposite directions as well.

Why does subnetwork stop there.

[MikeMillerGIS]

What condition barriers do you have defined on your tier?  Compare these to what is set on the line.  Did you add propagation to your water network?  Can you share a sample dataset?

[Rohanrajan]

Condition barriers set in tier definition

Network Attribute: Valve Status
Condition: Closed

No Propagation added in network.

[MikeMillerGIS]

Without a sample dataset or more information, I cannot provide any additional assistance.  There are lot of variables.

[RobertKrisher]

Unless you're using the "use digitized direction" option, the digitized direction of the line doesn't matter. If the trace stops at the junction, and includes the junction in the returned features, then the junction is a barrier. Check its attributes against the condition barriers of your trace (lifecycle status, device status, etc).

If the trace doesn't select the junction, its actually stopping at the line (this is the more likely scenario) which means that the line itself is a condition barrier. Once again, compare the attributes of the line against the condition barriers of your of your trace.