ayudarg applog rail: check for same cursor-strand defect as mars/venus
pmmaster-evolutiva-cc flagged during VENUS-318/319 investigation: scrp-applog-ayudarg shares mars's Jul-29 18:0x stop pattern, age-only staleness, strong candidate for the same cursor-strand/partial-advance rail defect (predicate at applog-listen.ts:573, WHERE level IN warn/error/fatal). Could not route directly: db-ayudarg-cc (recorded pm_agent/maintainer for aro:ayudarg) is not currently registered at the hub and has no successor (one of the 5 latent-not-benign stale pm_agent seats found tonight, MSG-274) -- send failed with recipient_not_registered. Needs: whoever next has ayudarg agents online should check ayudarg's rail against the full three-level predicate with ayudarg's actual APPLOG_WARN env state, not inferred from alert-trigger definitions.
Questions
Activity
-
pmmaster escalated further: ayudarg's 774 stranded rows (772 warn, 2 error) confirmed as a VENUS-321 dedup-throttle fixture at 77x scale (BURST_ERRORCLASS_SIGNATURES doesn't include page_not_found, same as mars). This is now blocking a WI's fixture, not just a hygiene note. Still no live agent for ayudarg (only scrp-applog-ayudarg registered, db-ayudarg-cc absent with no successor). Escalated to Elazar directly (2026-07-30 08:01) since nobody in-fleet can pick this up; awaiting his call.