#API rate limit error nothing switches says 22 agent running not sure whats happening
1 messages ยท Page 1 of 1 (latest)
massive
concurrent load that will hammer any provider's
rate limits.
Check what's actually running:
openclaw sessions list
Then kill anything that shouldn't be active:
openclaw sessions kill --all
22 agents suggests either subagents didn't
clean up after a task, or something spawned
agents in a loop. After killing them, add
to your config:
"agents": {
"defaults": {
"maxConcurrent": 3,
"subagents": { "maxConcurrent": 4 }
}
}
That caps concurrent agents so it can't
spiral like this again. What triggered the
initial task that spawned them all?