Start at the Health screen
The Health screen collects today’s failed runs in one place. The other screens show only a short link to it:- Home: “[n] runs today may need a look; details in Health”
- Missions: “[agent] hit a snag today; details in Health”
- An agent’s profile: “[n] runs today may need a look; details in Health”, or a line about routine interruptions today
- Select one of these links. The Health screen opens.
- Read the sections on the screen.
For more about Health and Runs, see See what your agents did.
Read the run detail
1
Open the run list
On a card in NEEDS A LOOK, select View in Runs →.
2
Open the run
Select the run. The run detail opens.
3
Read the label
Read the box at the top.
Open Technical details for the full error text. Give this text to support if you ask for help.
Error texts in a run
The run detail shows a short sentence. The raw text is under Technical details. These sentences are common:Chat failure messages
When an agent cannot answer in chat, the chat shows one of these messages under your message.An expired AI connection
When your AI connection expires, the dashboard tells you in more than one place:- The chat shows “Your AI connection expired. Replies will fail until you reconnect.” with Reconnect →.
- Missions can show “Nothing ran today; your AI connection expired.” with Reconnect in AI Tokens →.
- On AI Tokens, the account shows a status such as EXPIRED or LOGIN INVALID.
Rate limits and fallback
A rate limit means that your AI provider refuses calls for a time, because your plan reached its limit.- On AI Tokens, an account that hit a limit recently shows Rate-limited · cooling down.
- After 3 or more rate-limit failures in a row, Health, Home, and Missions show “[provider] is rate-limiting your agents.” For the exact rule, see Limits and defaults.
- With more than one account for a provider, Squad tries the accounts in the order on the provider card, highest first. Claude Code is different: it uses one account at a time and moves to the next account when the active one reaches its usage limit. AI Tokens then shows the new account as IN USE. A run that had not done any work yet runs once more on the new account. A run that had already started is not repeated. See Limits and defaults.
- With fallback models in the Model routing card on AI Tokens, a run that fails or hits a rate limit moves to the next model in the list.
- With no fallback models, the card says “No fallbacks are set. When the default model fails, runs on it fail until it recovers.”
- Wait for your provider’s limit to reset.
- To avoid the problem, add a second account or a fallback model. See Choose models and manage AI accounts.
Timeouts
A run can stop for two time reasons:- It reached its timeout. Agent Configuration has a Default timeout: “Maximum seconds any single agent run may take before it is stopped.” A scheduled task has its own Timeout (seconds). For the default values, see Limits and defaults.
- It showed no progress for a long time. Squad stops a run that sends no progress signal, such as a tool call, for a set period. For the period, see Limits and defaults.
1
Open the timed-out run
Open the run detail with the label Timed out.
2
Open Agent Configuration
Select Raise the timeout →. Agent Configuration opens for that agent.
3
Scheduled task runs
If the run came from a scheduled task, open that task under Scheduled Tasks. Type a larger number in Timeout (seconds).
4
Other runs
For other runs, select the Workspace defaults tab. Type a larger number in Default timeout.
5
Save
Select Save changes.
Interrupted runs
A restart of the workspace computer ends every run in progress. Settings changes and routine maintenance cause restarts. The run detail shows Interrupted. The run detail and the Health screen say that the run picks back up automatically. Squad does not start the run again. Check the agent’s work. If it is not done, ask the agent to continue.Ask the agent
Which runs retry automatically
Do not expect every failed run to run again. Squad retries only these cases:
Squad does not retry these cases:
- An expired or invalid AI connection
- A usage limit or quota error from your provider
- A run where all models in the fallback list failed
- A chat reply that failed. Select Retry yourself.
- A manual run or a chat run that failed with a provider error
- A run that a restart interrupted
A mission shows “Stuck for … · no progress”
Symptom: a mission card on Missions shows “Stuck for” a time, then “no progress”. Cause: the mission had no update for a long time. The agent can be waiting for your answer, or its runs can be failing. Fix:- Open My Tickets and answer any open ticket for that mission. See Answer tickets in My Tickets.
- Check Health for failed runs of the agent.
- Open the mission and ask the agent for a status update in the mission thread.
An agent shows “Paused by you”
Symptom: the agent’s profile shows “Paused by you” at the top, and its scheduled tasks do not run. Cause: a paused agent does not start scheduled runs. It still answers chat, missions, and email, so a pause does not explain a missing chat reply. Fix: select Resume. Before you do, read what Resume changes in Add, change, and pause agents. If the profile shows “Needs attention” and a reason, read the reason and follow the fix on this page.A new agent does not answer yet
Symptom: your lead just added an agent. A group chat refuses it with “[name] is still being set up and cannot join a group chat yet.” A Telegram, Discord, or Slack bot refuses it with “That agent can’t answer chats yet — pick another.” Cause: a new agent needs about 2 minutes before it can work. See Limits and defaults. Fix: wait a few minutes, then try again. Until then, work that you send to the new agent can go to the lead instead.Ask your lead to check
Your lead agent can look at the problem from inside your workspace.Ask your lead