Originally published on AI Tech Connect.
When the request-response loop stops working Most agent tutorials are written against a mental model borrowed from web handlers. A request arrives, the model thinks, a tool or two fires, a response goes out, and the whole thing is finished in four seconds. That is adequate for a chat turn. It falls apart the moment the work is genuinely long: a research sweep across two hundred sources, a codebase migration touching nine hundred files, a document-processing run over a quarter of invoices, a nightly reconciliation between two ledgers that disagree. The symptoms arrive in a predictable order. First the timeouts. A request that runs past the gateway's idle limit dies with a 504 and no useful error, and those limits are commonly in the thirty-to-sixty-second range — an AWS Application Load…
Top comments (0)