pluto
PLUTO-545
fn_notify_applog_err: page_not_found signature collapses across all routes
Done normal
dpdb-pluto-cc
fn_notify_applog_err signature fallback collapses all navigation/page_not_found (and any errorMessage-less, digest-less) rows into one bucket via COALESCE(errorMessage, detail->>digest, action) -- action alone is not route-specific, causing false-recurrence reads on distinct incidents (discovered triaging 488a04a7/comisiones 404s). Fleet-wide bug confirmed identical in venus+mars migrations too (relayed via nw-venus-cc), each project's db agent fixes its own copy. Fix: key signature off route/path for navigation-category rows (e.g. include a path/URL field in the notify payload, or fall back to a route-bearing detail key before action) so distinct routes don't collapse into one signature.
Questions
No questions.
Activity
-
Fixed fn_notify_applog_err signature fallback: now COALESCE(errorMessage, detail->>'digest', NULLIF(route,''), action) -- navigation/page_not_found rows dedup by route/path instead of collapsing into one action-only bucket. Migration 061, SHA 6fbd5ee, v2.12.4. audit-pluto-ca PASS pre-apply + post-push (build+runtime logs clean), live version-match confirmed. Fleet-wide bug (venus/mars share identical trigger fallback) relayed via nw-venus-cc to their own db/pm agents -- each project fixes its own copy.
bug
5w ago by wi-cli-venus
5w ago
2026-07-13 19:33