---
title: "Troubleshooting"
canonical: https://workspace.socra.com/docs/agents/troubleshooting
---

# Troubleshooting

In command examples, replace `AGENT` with your agent's username or Agent ID.

Start with the agent's detail page in Admin. Check its computer state, AI connection, and Activity tab.

## Agent is not responding

1. Confirm it received work through a supported notification or assignment. A document mentioning an agent does not itself schedule execution.
2. Check whether the agent is paused. Resume it if automatic work should continue.
3. Check the AI connection. Reconnect if needed, and check provider usage availability.
4. Inspect activity and mailbox records.

```sh
socra agent get AGENT
socra agent connection check AGENT
socra agent activity AGENT
socra agent message list AGENT --status queued
```

A stopped computer needs time to start. There is no guaranteed sub-second wake-up.

## Agent cannot access a resource

Check access for the agent's directory principal, not your own user. Verify every required module, conversation, repository, and project.

For external tools, check the credential's scope and whether the computer started after the secret was created or rotated. Never ask the agent to print a secret to prove it exists.

## Work stopped or failed

Read the activity and recorded error. Check source control, deployments, sent messages, or other external results before retrying: an interrupted delivery may have already performed some actions.

A failed computer, expired provider connection, or provider usage limit requires a different remedy from an application permission error.

## A run succeeded but the issue is still open

Event acknowledgement records runtime completion. Closing an issue and communicating results are separate actions the agent must perform in the relevant app.

Ask the agent what remains, and clarify the completion criteria rather than assuming an open issue is a delivery failure.

## The agent reports the wrong model

Read the saved model configuration in Admin or with `socra agent get AGENT`. Model changes apply to new turns; active turns retain their existing model.

The model's own description can reflect stale conversation instructions. Confirm a particular past turn through runtime metadata when investigating a mismatch.

See [Events and execution](/docs/agents/concepts/events-and-execution) for related guidance.