Share:

CMN stage audit

Every CMN lead Wed 4 Nov – Tue 17 Nov, checked against every 6AB, 5AB, N1N and R row that person still has anywhere back to Fri 8 May. Reaching a stage is meant to consume the one before it, so every row found here is one that should have disappeared and did not. Newest lead in the feed: 2026-11-17 12:46:42. Every leftover sat in the same city as its CMN, so the person-matching holds.

Original code→ chase → R→ re-SMS, sends a picture → N1N→ free for a chat? → CMN  — each step is meant to CONSUME the one before it
CMN in the window
333
people · 333 rows
Shifted cleanly
282
84.7% — nothing left behind
Still carrying an old stage
51
15.3% · 63 rows that should have gone
The shift itself failed
0
old stage within 14 days of the CMN
Two different faults — do not add them together. 0 people (0 rows) carry a stage row from within 14 days of their CMN: that is the shift failing to consume the previous stage. 51 people (63 rows) carry one older than that — an earlier journey that died and was never cleaned up. Different causes, different fixes.

What is left behind

A person can be counted under more than one stage, so these do not sum to the total.

Stage still livePeopleOf all CMN Rows within 14dRows older
6AB27 8.1%333032
5AB3 0.9%33305
N1N20 6.0%333020
R6 1.8%33306

How long before the CMN was that row created?

A same-day leftover is unambiguous: the lead converted and the previous stage was simply never cleared.

Gap6AB5ABN1NR Rows
31+ days32520663 100.0%

Which combination is left

Stages still live for that personPeople
6AB23 45.1%
N1N16 31.4%
R4 7.8%
5AB3 5.9%
6AB + N1N3 5.9%
6AB + R1 2.0%
N1N + R1 2.0%
Download the cleanup list — every leftover row (CSV)
R is the biggest single fault, and it is not subtle. Of the 0 leftover rows dated the SAME DAY as the CMN, 0 are R codes. The lead converts and its R row is simply never cleared — same person, same day, both rows still live.
R rows still live
0
within 14 days of the CMN
Of those, same day
0
— — no ambiguity at all
Distinct R codes affected
0
it is not one broken feed

The R codes not being cleared

Every one of these is {CITY}{SOURCE}R — the chase stage of a lead that has since converted.

R codeCityRows still live
Original code→ chase → R→ re-SMS, sends a picture → N1N→ free for a chat? → CMN  — each step is meant to CONSUME the one before it
Push gap: Sun 8 Nov, Sat 14 Nov, Sun 15 Nov carried almost no recycled leads at all against a median day of 263, while total lead flow held up. That is the recycled push stopping, not a quiet day.

Leads in, by stage, per day

Recycled counts every stage row plus CMN once each. The last day in range is always part-built.

DateAll leadsRecycled 6AB5ABN1NR CMN
Wed 4 Nov3,264516 15.8%1252817115042
Thu 5 Nov2,961375 12.7%56517112517
Fri 6 Nov2,322251 10.8%1421455832
Sat 7 Nov1,96274 3.8%2254115
Sun 8 Nov1,75113 0.7%41341
Mon 9 Nov2,231469 21.0%149387014962
Tue 10 Nov2,436499 20.5%202551076372
Wed 11 Nov2,800351 12.5%94424412644
Thu 12 Nov2,392263 11.0%17242018616
Fri 13 Nov2,363117 5.0%8139789
Sat 14 Nov1,9465 0.3%20120
Sun 15 Nov1,8310 0.0%00000
Mon 16 Nov1,821276 15.2%56402113425
Tue 17 Nov1,15778 6.7%3174288
TOTAL31,2373,287 10.5%7602578201,114333

By city

CityCMN peopleStill carrying an old stage Shift failed (≤14d)
New York7811 14.1%0 0.0%
Chicago5910 16.9%0 0.0%
Florida456 13.3%0 0.0%
Houston378 21.6%0 0.0%
Nashville353 8.6%0 0.0%
Dallas315 16.1%0 0.0%
Orlando265 19.2%0 0.0%
Boston223 13.6%0 0.0%
Yes — and that is what makes the leftovers a fault rather than the design. A CRM pull shows a code as it stands now, so an in-place shift is invisible unless the same row was observed earlier. Across 2,952 rows with an earlier observation on file, 93 were caught mid-shift: the row's own code was rewritten to CMN and the old stage genuinely disappeared, exactly as intended. 0 ever moved the other way.
Rows observed twice
2,952
the only rows that CAN show a shift
Shifted in place to CMN
93
the mechanism working correctly
Unchanged
2,859
96.8%
Shifted OUT of CMN
0
CMN is an end state

Every shift caught in the act

WasBecameRows
NYN1NNYCMN12
FL6ABFLCMN8
NA6ABNACMN8
FLN1NFLCMN7
NY6ABNYCMN7
CHIN1NCHICMN6
FL5ABFLCMN6
NAN1NNACMN5
HOUN1NHOUCMN5
DAL6ABDALCMN5
NY5ABNYCMN4
CHI5ABCHICMN4
ORLN1NORLCMN3
CHI6ABCHICMN3
BOS6ABBOSCMN2
DALN1NDALCMN2
ORL6ABORLCMN2
NA5ABNACMN1
ORL5ABORLCMN1
DAL5ABDALCMN1
HOU5ABHOUCMN1

What this count can and cannot see

A shift that happened before the row was ever observed is invisible and always will be — the ledger only started recording on 25 Aug 2026, seeded from /recycled-codes' chunk cache. So the shift count is a floor. It grows on its own as the ledger accumulates, which is why this report runs daily: a night not run is evidence that cannot be recovered later.