Before = the lane the pin left, 90 days before the switch. After = the new lane since the switch. Matured = 30+ settled orders on the new lane. Click a row to filter the pin table.
Switched on
Direction
By
Pins
Orders on new lane
On new lane %
Settled
Matured
RTO before
RTO after
Change
Better
Holding
Worse
Too early
Leaking
Pins
How to act on a bad switch · switch it back from here
Press Act on worse (sets Outcome = worse, 30+ settled). Worse = RTO 8+ points higher on the new lane with 15+ settled on both sides. Leaking rows are a UC routing fault, not a lane decision: fix the rule, do not switch.
Read Before vs After and Scorer now. Rows the page cannot act on are greyed with the reason: in cool-down (switched under 10 days ago), locked (bounced twice in 90 days), or Shadowfax has closed the pin (cannot go back there).
Tick the rows and press UC rule spec · switch back ticked. One txt file: pulls that went worse get a new SHADOWFAX rule (and the pin must be removed from the SHIPROCKET rule that pulled it, named per pin); pushes that went worse get a new SHIPROCKET rule.
Deploy in Uniware as the file says, check the rules JSON, then tick the same rows and press Switch-backs completed in UC. They are logged with the outcome and the rule name, go into cool-down, and this page watches the new lane from the next batch.
Pin
City
State
Band
Direction
Switched on
Days
By
On new lane %
Orders new lane
Settled
Before
After
Change
Outcome
Scorer now
Lane now
Outcome rule (review): better / worse = RTO moved 8+ points with 15+ settled on both sides; holding = inside that; leaking = over 10% of post-switch orders still on the old lane; re-opened = Shadowfax re-opened the pin and UC went back on its own; too early = under 30 settled on the new lane. Scorer now = today's Pin Health verdict for the pin (return = the return rule says go back to Shadowfax).