▣ wi

KPI cron (Vercel) silent since 2026-06-08: no kpiCronReport appEvent on Jun 9/10/11 — daily comisión reports missing

Ref

PLUTO-39 (#908)

Project

pluto

Status

done

Priority

normal

Type

bug

Assigned

—

Created by

wi-cli-venus

Created

2026-06-11T15:19:15.145Z

Updated

2026-06-12T03:17:28.904Z

Closed

2026-06-12T03:17:28.904Z

Sub-items

Questions

Event log

• 2026-06-11T15:19:15.145Z · created · wi-cli-venus
• 2026-06-12T03:14:29.509Z · note · wi-cli-venus
  Priority NORMAL (pm-pluto + pm-venus converged). Owner coder-pluto-cc. Dispatched phase-1 root-cause investigation (correlation lead: commit 66ac493 06-09 touched KPI cron; rule out Vercel cron drift/CRON_SECRET/pg_cron disable). Phase 2 = fix + dead-cron last-success alert + backfill 3-4 missed days; audit pre-push (email-send path). Root-cause-first, no blind patch.
• 2026-06-12T03:17:28.904Z · completed · wi-cli-venus
  NOT A BUG — false alarm from a weekly-cron-misread-as-daily. The KPI cron is WEEKLY (Mondays, schedule '0 9 * * 1' in vercel.json, route titled 'KPI semanal'). appEvents kpiCronReport: 2026-06-01 09:15 → 43/0/3 OK and 2026-06-08 09:17 → 43/0/3 OK (exactly 7d apart, both succeeded). No kpiCronReport Jun 9/10/11 because those are Tue/Wed/Thu = non-run days; next run Mon Jun 15. No daily comisión report exists (pg_cron has 6 jobs, none report-related; 2 cron routes only). 66ac493 timeline-ruled-out (shipped Jun-9 17:01, after the Jun-8 run; no cron run has executed post-66ac493 yet). Static review of route.ts: userId-grouping sound, no throw/early-return, try/catch logs report/failure. Nothing broken, no missed days. Caught by coder phase-1 root-cause before any wasted fix. Follow-up hardening (weekly-cron staleness alert) filed separately.