The HTTP 429 That Turned Seven Minutes Into Zero Work

This is a submission for DEV's Summer Bug Smash: Smash Stories powered by Sentry.

ARGUS is a data-catalog governance swarm. Its agents use structured model calls to draft descriptions, classify sensitive fields, and review repairs before anything can be written.

During a 45-entity sweep, the system spent seven minutes producing zero proposals. The report called the result review failed.

The endpoint was reachable. Health probes returned 200. The logs showed only:

429 Too Many Requests

The HTTP 429 That Turned Seven Minutes Into Zero Work

Related reading

When a Safety Reviewer Rejected Everything and Still Passed Its Test

I Used Sentry to Expose a Silent Data-Loss Bug with Zero Errors

Nine green tests and a parser that never worked once

The API promised industry keywords. Modern sites kept returning [].

Gotcha: chasing a bug that was never in my code

The cleanup that could never run: a silent Web Push leak in Go