‘3 AI tasks are already running’ (AI task limit)

You might be here because: “3 AI tasks are already running” · “Your account already has 3 agent turns running” · “Your account already has 3 AI turns running on Driftstack’s included AI” · “AI task limit reached” · “the AI won’t start my task” · “why does it say a limit when I only have one session” · “429 when sending a message to the agent” · “AI is busy / can’t send” · “A usage limit was reached. Wait a moment or review your plan, then try again”

Short answer

At most 3 AI tasks can run at the same time across all of your sessions. If you send a fourth, it is refused with “Your account already has 3 agent turns running (limit 3). Wait for one to finish, then try again.” or, on Driftstack’s included AI, “Your account already has 3 AI turns running on Driftstack’s included AI (limit 3). Wait for one to finish, then try again.” Wait for one task to finish, then send the message again. This is separate from the concurrent-session limit.

Check first

• Do you have AI tasks running in other sessions or on another computer? Each running turn counts.
• Is a task still finishing after you pressed Stop? It keeps counting until it actually ends.
• This sentence covers four limits. What were you doing? Launching a profile → sessions at once (Concurrent session limit reached (429 concurrency-limit)) or, after a plan change, After a downgrade only the most recently used profiles/proxies can launch; creating or duplicating a profile → Cannot create a profile: plan’s saved-profile limit reached; sending a message to the AI → ‘3 AI tasks are already running’ (AI task limit).
• The message you tried to send was not run at all, so it is safe to send it again once a task finishes.

Likely causes and fixes

1. Three tasks are in flight. The server answers HTTP 429 rate-limited, title “Too Many Requests”, with one of the two sentences above. The desktop app shows a generic “A usage limit was reached. Wait a moment or review your plan, then try again.”. Fix: wait for a task to finish, then resend. From code: the type is rate-limited, not the session limit’s concurrency-limit. Depending on how your account’s AI is billed, the same limit can instead answer 429 concurrency-limit with ai_tasks_in_flight: true and the sentence “3 AI tasks are already running. Start this one when one finishes.”; the fix is the same.

2. From code you may see retry_after_seconds: 5. No step ran either way. A task usually takes longer than that, so wait for one to finish rather than retrying every 5 seconds: asking again every 15 seconds is enough, and keeps waiting tasks from using up your message rate.

3. A task looks finished but is not. A turn that hit Stop keeps running until the server ends it (see Still finishing the previous task). Give it a moment.

If it still fails

If you are sure fewer than three tasks are running and the refusal keeps coming for several minutes, press Talk to a person in this chat (or open Help) and include the time, the session ids involved and the exact message. The limit itself is fixed at 3 and is not something support can raise per account.

Related

• Concurrent session limit reached (429 concurrency-limit)
• ‘Still finishing the previous task’ — Send is held