Find out why a model account isn't running tasks
Each run picks an enabled account that fits its task and has room. When an account sits idle while tasks wait, the AI Accounts list says why: in the round mark before its name, the chips beside it and the state of each node it runs on. This guide reads them in that order.
Who can do this: anyone who can open AI Accounts. Enabling an account needs the Org Owner or Org Admin role; signing one in needs the system create permission. A member whose role can't view every account's status sees only the round mark, with no node rows.
- In the sidebar, select Directory, then AI Accounts.
- Read the round mark before the account's name:
- ● available. Go on to step 3.
- ⊘ disabled. Select Enable in its ⋯ menu, or Disabled in the Enabled column.
- ▲ quota at 80% or more, or its usage limit hit. See Check how much of a model account's quota is left.
- ✕ failing or blocked. Its sign-in was refused, or its nodes are blocked; go on to step 3.
- ◌ initializing: it was signed in a few minutes ago. Wait for a node to report it.
- Read the chips beside the name, and hover each one for its reason:
- explicit only: Auto-assign is off, so the account runs only tasks that pick its provider. See Limit how a model account is used.
- limit hit: a runner hit the account's limit. It is out of rotation until the limit resets.
- rejected: the provider refused the sign-in. Select Re-login in its ⋯ menu.
- no credentials or no key: it was never signed in, or an API-key account has no key stored.
- Hover a ⚠ after the name to see which node needs attention. When the row says Not signed in on any node yet. or Its node was removed., select Sign in or Add to node in its ⋯ menu.
- Select ▸ beside a subscription's name to list its nodes, and read each node row's state:
- ok: the node can run it.
- Login: the node needs a sign-in. Select it to sign the account in there. Without the permission to sign in, you see the reason instead: missing, needs login or can't read. See Sign a model account in again.
- Not synced: the sign-in has not reached the node yet. Hover it for the reason, or select Login in the node row's ⋯ menu.
- Syncing… or provisioning: the node is still setting it up. Wait.
- refresh locked, refresh failed or usage check failed: retried at the node's next check. Nothing to do.
- Billing or Seat: signing in again won't help. Pay the subscription, or ask the provider account's administrator to restore the seat.
- Check that the waiting task can run on this node and provider. A subscription runs only on nodes where it is signed in; a task that picks another provider never uses this account.

If every account is healthy and tasks still wait, they may be waiting for room: each account runs at most its Max runners, and your plan caps how many agents run at once.
Related
- How model accounts work: how a run picks an account, and account health.
- Model accounts: every mark, chip and node state.
- Pause or remove a model account: when an account should stay out of rotation.