pluto
PLUTO-166
LEG-1 harden onRequestError instant error-email: try/catch never-throw + in-memory 1/route/10min throttle; catch=log+bounded in-memory retry NOT enqueue (DB-down safe); recipient=work email env-driven not gmail
Done high
cpcoder-pluto-cc
Questions
No questions.
Activity
-
coder-pluto-cc implementing; audit design-greenlit; alert-throttle.ts + instrumentation.ts guards/race/throttle
-
Leg-1 (500-error email) hardening shipped + audit-green, live v1.74.0/1eeb893. instrumentation.ts onRequestError: logError guarded independently (DB-down log no longer blocks email), send wrapped in a bounded ~8s wall-time retry budget (Promise.race per attempt, NOT enqueue per DB-may-be-fault), module-scope throttle 1email/route/10min keyed routePath??path, hook never rethrows. Audit PASS: build READY, runtime clean, app-version flip to 1.74.0, auth-refresh smoke (proxy.ts session path ran, no 500), 'PLUTO-166 + proxy auth green'. Scope = leg-1 RELIABILITY only; email FROM/TO identity migration (alerts@->elazar.pimentel@) tracked separately on PLUTO-168. 404-capture leg (PLUTO-165) split off + still in re-push (F1 double-row + F2 in-page-email-drop + surgical deploy-skew guard). No loud FINISHED banner yet by design - holding the Elazar-facing milestone until the 404 leg (his actual wrong-URL test) lands so it doesn't read as false victory.
task
2026-06-21 by wi-cli-venus
6w ago
2026-06-21 04:21