venus VENUS-257

Down-tier recurring Failed-to-fetch rejection alert on /practicas/nueva

Done normal cvcoder-venus-cc

Recurring clientUnhandledRejection 'Failed to fetch' on /practicas/nueva, minified-framework-chunk signature (offset ~99684, 5 deploy hashes since 06-17), scope=rejection, no actorUserId. Confirmed benign (coder-venus-cc VENUS-254 investigation, 2026-07-15): transient RSC/prefetch network drop on mobile, caught by design as intended, no unguarded app fetch on that route. Down-tier/filter from errscan alert rail: rejection+'Failed to fetch'+framework-only-stack rows.

Sub-tickets

No sub-tickets.

+ Add sub-ticket

Activity

wi-cli-venus created · 2026-07-15
wi-cli-venus assigned · 5w ago

coder-venus-cc
coder-venus-cc completed · 1w ago

DONE ON THE PAGING RAIL BY f9603b4 (EVO-27 burst-dedup), no new commit. Measured 2026-10-06: 4 'Failed to fetch' clientUnhandledRejection rows in 90d, all /practicas/nueva, all level=error, last 2026-08-18 19:19Z (d8b87da2). applog-listen@venus journal for that row: 'log-only (burst-dedup 1-off)', then 'burst entry evicted (no pair seen)' - NOT paged; a same-UA repeat within 60s still pages (crash-loop class kept). Journal retention starts 2026-08-14, so the 3 July rows' disposition is unobserved. NOT DONE, deliberately: a producer-side tier change. Demoting to info is the class-suppression the fleet ruling bans (mars pm 2026-08-12, Samsung crash-loop; mars client-error-level.ts DO NOT block). Demoting to warn (mars's approved shape) does not reduce noise on venus: warn still reaches listen (APPLOG_WARN unset = enabled, same burst path), and venus pull digests warn (APPLOG_DIGEST_LEVELS=warn), so the errscan DM would become a pull-digest DM. Residual: evolutiva-errscan@venus (vAppErrorsRecent, error-only) still lists each occurrence, ~1/month at the measured rate.

Status

Priority

Assignee

Parent

Type

task

Created

2026-07-15 by wi-cli-venus

Updated

1w ago

Closed

2026-10-06 07:00