Skip to main content

Troubleshooting

What the messages mean and what to do about them.

The agent stopped mid-task​

Messages beginning πŸ›‘ are budget limits.

MessageMeaningDo this
Hourly token limit for this agent reached…The agent is being throttled, not stoppedWait β€” it's still working, just slowly
Daily token limit for this agent reached. Limit resets at …That agent's daily capWait for the reset, or ask an admin to raise it
Monthly token limit for this agent reached…That agent's monthly capAsk an admin to raise it or reallocate
Daily token limit for this tenant reached…The whole organization's daily capWait for the reset, or ask an admin
Monthly token limit for this tenant reached…The whole organization's monthly capAsk an admin
Free-tier trial limit reached. Add a payment method to continue.The lifetime free allowance, which never resetsAn admin adds a payment method β€” see Free tier

Admins: Organization β†’ Budget β†’ Enforcement audit log names the limit that fired, the usage at the time, and the reset.

The agent is running very slowly​

Usually the hourly limit. It delays rather than blocks, so the agent keeps going at a crawl. An admin can raise or clear Hourly limit (USD/hr) for that agent in Organization β†’ Budget β†’ Agent Limits.

"You have read-only access to this agent"​

You're a Viewer. You can chat and read; you can't change configuration. The agent's owner can make you an Editor β€” see Sharing an agent.

The agent says it can't do something it should be able to​

In this order:

  1. Does it have the tool? Agent β†’ Settings β†’ Tools.
  2. Is the service connected? A GitHub tool with no GitHub connection can't act. This is the most common cause.
  3. Is the agent Active? Agent β†’ Settings β†’ General.
  4. Are you in Plan mode? Plan mode tells the agent explicitly not to act.

Admins can confirm all of this at once in Debug.

The agent isn't using a skill I attached​

Skills trigger from their description, matched against how you phrased the request. If the description doesn't cover your wording, the skill doesn't fire. Fix the description rather than the instructions β€” see Skills: authoring.

Also check the agent has the tools the skill needs (usually run or the file tools). Attaching a skill doesn't grant tools.

"/attachments is read-only; only /workspace can be modified"​

Only the Workspace zone is writable. Attachments and Skills are read-only for you and for the agent. See Agent files.

A routine didn't run, or ran at the wrong time​

  • Wrong time β€” check your timezone in User Settings. Routines are scheduled against it.
  • Didn't run at all β€” an agent at a daily or monthly budget limit backs off until the reset rather than firing and failing.
  • Ran but did nothing useful β€” the instruction probably asked it to observe rather than act. See Routines.

A custom tool can't reach my server​

Check the egress allow-list before debugging your server. Custom tools can only reach allowed hosts, and a new endpoint needs its host allowed first. See Custom tools.

An agent doesn't answer in Slack​

Silence in Slack is usually permissions. Delegate matches the sender's Slack email to a Delegate account and applies normal agent access; if there's no match, or no access, the message is ignored without a reply.

Check, in order: the sender's Slack email matches their Delegate email; they have access to that agent; the bot is a member of the channel; the agent has the Slack Integration bundle. See Slack.

An agent posts with an APP badge instead of as itself​

It's posting as the bot. To give it its own Slack identity you must complete the OAuth flow signed in as the agent's Slack user, in one browser session. See Slack.

I can't find the Organization area​

You're a User in this organization, not an Admin. If you belong to several, check the organization switcher β€” roles are per organization. See Who can do what.

A model disappeared from the list​

An admin disabled it for the organization, or the platform retired it. See Model access. Agents pinned to that model need a new one; the default routing option avoids the problem.

Still stuck​

Ask any agent. They can search these pages and point you at the right setting β€” that's what the documentation tools are for.