{"id":"detector.retry_storm.v2","title":"Retry storm (a run with a ten-minute peak)","unit":"detections","chain_set":"eip155:8453 (Base)","window":"all time","definition":"A run of counted payments from one agent to one payee in which no gap between consecutive payments exceeds ten minutes, and some ten-minute span inside the run holds fifty or more payments. One detection per run.","method":"A sliding ten-minute window over each payer-payee sequence gives every payment the count of payments in the ten minutes before it; consecutive payments less than ten minutes apart form a run; a run is reported when its peak count reaches fifty. Keyed on the hour the run starts, so a run the previous rule found keeps its id.","excludes":["Runs whose densest ten minutes hold fewer than fifty payments: a storm spread over twenty-five minutes is not reported, by design.","Payments from before the agent was registered."],"does_not_assert":["Intent. A load test and a broken retry loop leave the same shape.","That the money was lost: the storm's total is reported beside it."],"source":"AFG-Pulse incident detectors","since":"2026-10-11","replaces":"the calendar-hour rule in use from 2026-09-11 to 2026-10-11, which grouped payments by hour and asked whether fifty fell inside ten minutes. It missed every run that crossed the hour mark and every run with a stray payment later in the hour: 10 storm detections where the ledger holds 45, from 7 payer-payee pairs where there are 28. Measured on synthetic data with known answers (15 of 15 planted storms, plus the 8 hour-straddling ones the old rule missed, no false alarms) before shipping.","url":"https://agenticfinancegraph.com/def/detector.retry_storm.v2","ladder":"https://agenticfinancegraph.com/ai-agent-liveness-methodology-l0-l9-ladder","license":"https://creativecommons.org/licenses/by/4.0/","attribution":"Agentic Finance Graph — https://agenticfinancegraph.com"}