This read-write INTEGER specifies the maximum number of connections that can be routed in one routing cycle. An administrator tunes this to control how aggressively PAR's Connection Manager works through a backlog of unrouted connections per cycle, balancing responsiveness against CPU load on the node. For example, after a major outage deroutes hundreds of PVCs, this cap limits how many are attempted per cycle so the routing engine doesn't overload the node while catching up.