Troubleshooting

Fixes for common problems with AgentOS. Sign-in codes, Google connection errors, blocked actions, paused workspaces, limits and deployment errors.

Check your spam folder and make sure the address is spelled correctly. You can ask for a new code once a minute, and a code works for 15 minutes. After five wrong tries a code locks; request a new one. Only the newest code works.

"Please wait a minute before asking for another code"

Codes can be requested once a minute. Wait a minute and try again.

Google says the app is not verified

Until Google finishes its review of AgentOS the connection may show this warning, and Google may limit who can connect. Choose Advanced and continue if you started the connection yourself.

"Google refused access" or "reconnect"

The permission was removed or never granted. Open Connections, disconnect Google and connect it again, ticking the permission the agent needs (Read email, Send email or Calendar events). Sending email needs the Send email permission.

The agent says a tool is not available

An agent can only use the tools in its own settings, and the workspace policy may hide some tools. Check the agent's permissions and its tool list. A connection must also be set up for the tool, such as Slack for Slack tools.

An action was blocked

Open the run and read the blocked step. Typical reasons:

Write access is off for the agent.
The workspace policy does not allow that email domain or Slack channel.
The needed connection is missing.
Suspicious instructions were found in content the agent read, so sending was turned off for that run. Review the content, then run again.

Nothing was sent after my real run

Real runs wait for approval. Open the Approvals tab and approve the action. If more than 48 hours have passed the request has expired and the agent must run again.

"Agents are paused for this workspace"

An admin used the emergency pause. Open Activity and choose Resume everything. Scheduled runs missed while paused are skipped.

"This agent is suspended"

An admin suspended the agent, or a marketplace listing it came from was removed. Open the agent and choose Reactivate this agent, unless it came from a removed listing.

Run limit, agent limit or budget reached

Your plan limits the number of agents, monthly runs and AI spending. The message says which limit you reached. An agent can also have its own daily run limit and monthly budget in its permissions. Limits reset at the start of the month (UTC), and daily limits at midnight UTC.

A deployment answers 401, 403 or 429

401 means the token is wrong or the deployment does not exist. 403 means the deployment is switched off. 429 means more than 30 calls in a minute, or the agent reached a limit. Create a new token from the Deployments tab if you lost the old one.

The agent did not remember something

Memory is matched to the request, so a note shows up only when it is related to what you ask. Memories that look like instructions to an AI are refused, and a run that read suspicious content cannot save memories. Add the note by hand from the agent's page if needed.

Still stuck

Open the run and read its steps, which show exactly what the agent did. Use the help chat on this page to ask a question.