Finding
Growth dashboard (2026-05-11) found that BigQuery telemetry has ingested zero events since 2026-03-14 (~2 months of gap). Last data point: 342 runs, 1 distinct user in the week of Mar 7-14.
This was not previously flagged. PR #739 was believed to have fixed telemetry ingestion, but either the fix didn't land in prod or a subsequent regression broke it.
Impact
- Growth dashboard BQ rows show stale data from March — WoW deltas are meaningless
- Cannot validate acquisition channel map goal (was depending on post-v0.3.1 telemetry)
- Cannot measure active users from CLI side
Next steps
Source
SELECT COUNT(*) FROM cli_events WHERE DATE(timestamp) >= DATE_SUB(CURRENT_DATE(), INTERVAL 7 DAY) → 0 rows for any date after 2026-03-14.
Flagged by: growth squad dashboard worker, 2026-05-11.
Finding
Growth dashboard (2026-05-11) found that BigQuery telemetry has ingested zero events since 2026-03-14 (~2 months of gap). Last data point: 342 runs, 1 distinct user in the week of Mar 7-14.
This was not previously flagged. PR #739 was believed to have fixed telemetry ingestion, but either the fix didn't land in prod or a subsequent regression broke it.
Impact
Next steps
Source
SELECT COUNT(*) FROM cli_events WHERE DATE(timestamp) >= DATE_SUB(CURRENT_DATE(), INTERVAL 7 DAY)→ 0 rows for any date after 2026-03-14.Flagged by: growth squad dashboard worker, 2026-05-11.