His session stopped at its limit; the test processes it started ran on for 17 hours and made about 59,000 API calls, roughly $2,000
An AI session started verification tests as background processes. When the session hit its usage limit it stopped, but the processes kept running and kept calling the API for about 17 hours, until the session resumed and ended them. Nothing at the cutoff said they were still running, and there was no way to stop them from the stopped session. The test loop had no cap on turns or calls. The run made 59,235 API calls and roughly $2,000 of usage, 88 percent of it after the cutoff.
$2,000at stake
This one went wrong. Read what happened so you don’t hit the same problem.
How it works
- Session starts verification tests in the background
- Session hits its usage limit and stops
- Background processes keep calling the API
- No warning at the cutoff and no way to stop them
- About 17 hours and 59,235 calls later the session resumes and ends them
- Roughly $2,000 of usage, 88 percent after the cutoff
Why it’s worth knowing
The session was stopped. Its processes were not, and the bill kept the two ideas separate for 17 hours.
Where it’s from
Summarized from a public post on github.com. See the original ↗