This boolean-style flag (encoded as yes/no rather than true/false, per the description) controls whether the device is allowed to fail this circuit over onto a non-preferred ring if the preferred ring(s) set via the EP1/EP2 objects become unavailable, and implicitly relies on the load-balancing mechanism to move the circuit back to its preferred ring once that ring recovers. Setting this to no means an admin has decided this circuit must strictly stay on its designated preferred ring(s) even at the cost of going down entirely if that ring fails, rather than automatically failing over. For example, a circuit with strict routing requirements (perhaps for regulatory or latency reasons) would have this set to no(2), so it goes down rather than silently rerouting through an unplanned ring path during a preferred-ring failure.