Failure class
Timeout or rate limit under machine pacing
At agent speed, the site returns 429s or times out.
Who it hits
Agents move faster than people; flows that pass manual QA fail at machine pace.
How to fix it
- Return 429 with Retry-After.
- Size rate limits for real agent concurrency.
- Test with machine-paced load.
How alt.qa detects it
We tag a finding as “Timeout or rate limit under machine pacing” when the trace shows this pattern at the blocking step. It only becomes a ticket once it is Confirmed (reproduced in two or more cells or by replay), and we show which personas and agents it hit.
In an Alt Matrix
Look for the pattern: a failing column usually means an agent-class problem; a failing row a persona problem; the same step failing in three or more cells a product bug.
See where agents fail on your funnel.
Run one free cell on a property you own. No sales call, no card.