Skip to content

Why is my Agent not responding or no longer working?

Check the work delivery, computer state, AI connection, and access separately. A computer can be running without an active task, and a connected AI subscription does not prove that the Agent received your assignment.

An Account owner or admin can perform the following checks in Admin. If you do not have either role, ask an existing owner or admin to check the Agent and share the relevant error.

  1. Open Admin, select Agents → Agents, and open the intended Agent.
  2. Check Computer → Status and any error. Sleeping allows automatic wake when supported work arrives. Paused blocks automatic work until you choose Resume work. Provisioning, Waking, or Upgrading means a transition is in progress; Failed needs the displayed error investigated.
  3. Under AI, check Connection. Use the connection recovery guide for an expired sign-in or Reconnect required. Check the provider's usage allowance as well as Socra billing.
  4. Select View activity. Find the relevant event and read its outcome or View error. Inspect the original Channels conversation, Cortex Issue, or scheduled Task to confirm the work actually reached the Agent.
  5. If access failed, check permissions for the Agent's own identity on the named resource. Your access does not transfer to it.

From an authorized CLI session, these commands read saved state without waking the computer. Replace AGENT with its username or ID:

socra agent get AGENT
socra agent activity AGENT
socra agent message list AGENT --status queued

Mailbox queued means waiting for delivery; delivered means handed to the runtime without an acknowledgement yet. An acknowledged event has an outcome, which may be succeeded, failed, or canceled. A successful event does not automatically close an Issue, publish a change, or send a reply.

If Workspace billing prevents the computer from starting, read the error and ask an Account owner to check Billing. Changing Socra billing does not fix a provider usage limit or a missing resource permission.

Before retrying interrupted work, inspect its actual effects: a commit, deployment, file change, or sent message may already exist. Do not assume that no action happened merely because the final response is missing.

Wake computer and socra agent connection check AGENT can start compute; the latter is a live Codex connection check, not a read-only status lookup. Use it only when you intend to start the computer and incur running usage. See Agent troubleshooting.