RC Migration Sync - 2026-06-07

Weekly safety-net check that compares RingSense Tasks to Litify Notes for the trailing 7 days and confirms Nathaniel's primary flow is healthy. Per the playbook, a real miss is created as a Litify Note only when the day-ratio analysis crosses into outage territory.

Window

2026-05-31 → 2026-06-07 (trailing 7 days).

Totals

RingSense Tasks: 1,037
Litify Notes with External_Id__c LIKE 'rc_call_%': 514
Overall naive ratio: 49.6%

Day-by-day

Day	Tasks	Notes	Naive Ratio	Class
2026-05-31 (Sun)	2	2	100%	tiny sample, window edge
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 band)
2026-06-05 (Fri)	199	90	45.2%	BORDERLINE — sits just above the 45% outage threshold
2026-06-06 (Sat)	3	2	66.7%	tiny sample, likely still processing

Settled multi-day average (5/31–6/4): 835 tasks, 422 notes = 50.5%, squarely inside the documented 50–63% normal band from the 2026-05-22 baseline.

Classification

No outage. Pattern consistent with the by-design upstream exclusion at RingSense's call-to-record association layer. Nathaniel's flow appears healthy.

Records synced this run

Zero. No Notes created. The day-ratio analysis did not surface a proven flow miss, so the playbook's "do not bulk-create Notes to fix it" rule applied.

Records missed (true)

Unknown count — not separately computed this run. See "Errors / limitations" below.

Errors / limitations

Salesforce SOQL MCP tool timed out (180s) on the full-record dumps (1,037 Task CallObjects in one shot). Aggregate count-by-day queries succeeded. The skill's per-day ratio test was performed and was sufficient to classify the run as healthy.
Bash sandbox returned ENOSPC partway through, so the precise sessionId-level diff was not performed for the full window. Per the playbook, ENOSPC is a known infra condition; routed remaining work through MCP only.
A small theoretical bias exists in the per-day ratio: a Note created on day X may correspond to a Task from day X-1 due to flow latency. The multi-day settled average smooths this out, which is why the settled 50.5% is the cleaner signal.