RC Migration Sync - 2026-06-05

Run date: Friday, 2026-06-05

Window: Trailing 7 days, 2026-05-29 through 2026-06-05

Mode: Read-only safety-net scan. No Litify Notes created.

TL;DR

No flow outage detected. Every settled day cleared the 45% match threshold. The unmatched set is the documented by-design RingSense upstream exclusion pattern, not a flow failure. Zero writes performed, which is the correct action.

Records Synced / Missed

Records synced this run: 0 (no proven misses on settled days)
Records missed (Tasks without a Note in window): ~621 across 7 days, all consistent with the by-design exclusion. None classified as proven misses.
Errors encountered: 0

Day-by-Day Match Ratio

Day	Tasks	Notes	Ratio	Classification
2026-05-29 (Fri)	217	123	56.7%	Normal
2026-05-30 (Sat)	8	4	50.0%	Normal (low volume)
2026-05-31 (Sun)	2	2	100.0%	Normal (low volume)
2026-06-01 (Mon)	188	95	50.5%	Normal
2026-06-02 (Tue)	275	150	54.5%	Normal
2026-06-03 (Wed)	177	86	48.6%	Normal
2026-06-04 (Thu)	193	89	46.1%	Normal (lower edge)
2026-06-05 (Fri, today)	199	90	45.2%	In-flight, weighted less
7-day totals	1,259	638	50.7%	In normal 50–63% band

SessionId Spot-Check (2026-06-04)

Pulled all 193 Tasks for 2026-06-04 and all 179 Notes from 2026-06-04 to 2026-06-05 to capture next-morning lag.

Matches are clean. Example:

Task CallObject RS~s-a71984024ba4cz19e8ffa0102z66a0d000000~3565212789052 ↔ Note External_Id rc_call_s-a71984024ba4cz19e8ffa0102z66a0d000000

Unmatched Task sessionIds observed:

s-a71984024ba4cz19e929dd250z68290ca0000
s-a7198422528eez19e929e996bz68955560000
s-a7198582de993z19e92a77632z68ae0060000

These are the upstream RingSense exclusion pattern, not flow misses. Consistent with the 2026-05-22 baseline.