Start on Today
When a teammate’s work did not finish today, Today and Needs you show a card for it, with the fix: Reconnect and an app’s name, Open AI settings, or See what happened. The owner and Administrators see these cards. See Fix work that did not finish. See what happened opens History with that teammate’s runs of the last 3 days, today first. Select a run to read its detail. See Read the run detail. For all of today’s run problems in one place, open Health. On a teammate’s About page, select the line about today’s runs, for example “2 runs today didn’t finish.” Health has these sections:
For more about History and Health, see See what your squad did.
Read the run detail
1
Open the runs
On a card on Today, select See what happened. On Health, select View in History on a card. History opens with that teammate’s runs.
2
Open the run
Select the run. The run detail opens.
3
Read the label
Read the box at the top.
When Squad shortened the error, Technical details shows 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. When Squad shortened the error, the raw text is under Technical details. These texts are common:
A run that failed because no AI account can run its model, for example with
No API key found for provider, has the reason “No AI account was connected for its model.” on its card on Today and in History, with Open AI settings. Squad for Mac shows the same.
Chat failure messages
When a teammate cannot answer in chat, the chat shows one of these messages under your message. In a teammate’s own chat, [name] is the teammate’s name. In a group chat, or on a message that another teammate sent, it says “your teammate”. A message that the teammate sent on its own, for example from a routine, can show the same sentences when its run fails. It has no Retry, because there is no message of yours to send again. Ask the teammate to try again.
In Telegram, Discord, and Slack, the teammate says the same in its own words after “⚠️”, for example that the Google AI key it uses is on Google’s free plan, and then “My backup AI model didn’t answer either.” when its backups failed too. When the disk of your cloud computer is full, it says “⚠️ I hit a problem before I could finish replying. Our cloud computer is out of disk space, so I couldn’t take this message. Ask your chief of staff to free up space, then send it again.”
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.
- A banner above every screen says “Claude Code is signed out, so your squad can’t work.” or “ChatGPT is signed out, so your squad can’t work.”, or “Claude Code and ChatGPT are signed out, so your squad can’t work.” when both are. The ChatGPT part shows only when every ChatGPT account that you connected has expired. While another ChatGPT account works, your squad uses it, and only AI names the expired account. Everyone in your squad sees the banner, and nobody can close it. The owner and Administrators read “Reconnect it and your teammates pick up where they left off.” with Reconnect, which opens Settings > AI. Other people read “[owner] can reconnect it in Settings → AI.” The banner does not show on AI in Settings. On Today and Needs you, it leaves out Claude Code, because the first row there says it.
- When your Claude Code account is signed out, Today and Needs you show “Claude Code is signed out, so your squad can’t work.” first. Everyone in your squad sees this row. Only the owner and Administrators get Reconnect Claude Code on it. See Fix work that did not finish.
- When Claude Code is signed out, the owner gets one email with the subject “[Squad] Reconnect Claude Code so your squad can work again” and Reconnect Claude Code, which opens AI. Squad sends it only while the account is still signed out. If the account signs out again later, the owner gets another email. It has no switch of its own in Settings > Notifications. See Notifications.
- On AI in Settings, the account shows a status such as Expired or Signed out, with Reconnect on its row.
- When Claude Code is signed out, a teammate on it answers in Telegram, Discord, or Slack with “Claude Code is not signed in on your cloud computer. Open Settings → AI in Squad and reconnect it.” Its failed run in History starts with “Claude Code sign-in stopped working. Reconnect the Claude account in Settings → AI.”
Claude Code reached its usage limit
When every Claude Code account that you connected has reached its usage limit, a line above every screen says “Claude Code has reached its usage limit.” and when your teammates pick up again, for example “Your teammates who use it pick up again tomorrow at 4:00 AM.” The time is in your own time zone. When Squad does not know the time, the line says “Your teammates who use it pick up again when it resets.” Everyone in your squad sees the line. A usage limit is not a sign-out. There is nothing to reconnect, and Squad sends no bell notification or email. The owner and Administrators who work with every teammate also get Add another account, which opens AI in Settings. The line goes away at the reset time, or sooner when a Claude Code run works again. While it shows, Today and Health do not repeat that Claude Code is limiting your squad. For when Squad shows the time, see Limits and defaults. In Telegram, Discord, or Slack, the reply of a teammate on Claude Code can say so too, for example “Every connected Claude Code account has reached its usage limit. The first one resets Nov 8, 04:00 UTC. You can also connect another account in Squad under Settings → AI.” The time in this reply is in UTC. Fix: wait for the reset, or connect another Claude Code account on AI. To keep work going during a limit, add a model under When it can’t answer. See Rate limits and fallback. Squad for Mac shows the same line, with the time in the Mac’s own format, for example “tomorrow at 4 AM”, and Add another account for the same people.Your cloud computer’s disk is low or full
Your squad works on its own cloud computer. When that computer’s disk runs low or fills up, every screen of the dashboard shows a banner. Squad checks the disk about every 30 minutes, and waits while a teammate is in the middle of a reply. See Limits and defaults for when a disk counts as low or full.- Low: an amber banner: “Your cloud computer has [free space] of space left.” Hide for a day hides it for a day in this squad, in this browser.
- Full: a red banner that you cannot hide: “Your cloud computer is out of space ([free space] left), so your teammates can’t save new work until some is cleared.”
Your cloud computer keeps running low on memory
A run on a Claude Code account waits for free memory before it starts. See A teammate says “Waiting for memory to free up on the cloud computer”. Teammates still work at the same time. A run waits only while starting it would leave too little memory free. When a wait took 2 minutes or more, every screen shows an amber banner. Shorter waits show no banner, however many there are. Everyone in your squad sees it. Squad sends no bell notification or email. For when it shows, see Limits and defaults. The banner has the same sentence for every cause, for example: “Your teammates had to wait for memory on your cloud computer 12 times in the last day, the longest for 37 minutes.” After one wait, it says, for example, “once in the last day, for 3 minutes”. When the log of waits is full, the count says “500 or more times”. The words after the sentence say what made memory run out:- Teammates start at the same moment. Most waits began while memory was still free, because several teammates had just started. The banner says “Most of those waits came when many teammates started at once, like teammates mentioning each other back and forth or routines set for the same minute.” When the banner has no Ask button, it adds “Your chief of staff can find what wakes them together.”
- The computer is short on memory. When the banner has no Ask button, it says that apps, previews and databases left running after a task are the usual cause, and that your chief of staff can find them and stop the ones nobody is using.
- When teammates start at the same moment, the button is Ask and your chief of staff’s name to find what wakes everyone at once, and the chat is called Teammates waiting for memory. The message starts “Our teammates keep waiting for memory on the cloud computer, mostly when many of them start at the same moment.” It asks the teammate to find out what wakes your teammates together, suggest how to spread them out, and check for apps, previews, databases, or test runs that are still going. It asks the teammate to ask you before it stops or changes anything.
- When the computer is short on memory, the button is Ask and your chief of staff’s name to free up memory, and the chat is called Free up memory. The message asks the teammate to find what uses the most memory, stop what nobody is using, and check whether many teammates start at the same moment. It asks the teammate to ask you before it stops or changes anything that it is not sure about.
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, the provider’s card shows Hit its limit, cooling down after a recent rate-limit failure on that provider.
- After 3 or more rate-limit failures in a row, the sentence on Today says “[provider] is limiting your squad right now.” Health says “[provider] is rate-limiting your teammates.” For the exact rule, see Limits and defaults. While the line “Claude Code has reached its usage limit.” shows, both leave Claude Code out. See Claude Code reached its usage limit.
- 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 then shows the new account as In use. The run continues once on the new account. If it had already done work, the teammate is told to continue from where it stopped and not to repeat what is done. See Limits and defaults.
- With models to try next in the Your squad’s AI card on AI, a run that fails or hits a rate limit moves to the next model in the list. When a model under When it can’t answer finishes the work, the failed attempt does not count as work that did not finish. History shows it as Picked up, with “Your teammate picked this back up and finished it.” See Limits and defaults.
- With no models to try next, the card says “Nothing set: when it can’t answer, the work waits until it can.”
- Wait for your provider’s limit to reset.
- To avoid the problem, add a second account or a model to try next. See Choose models and manage AI accounts.
Z.AI’s own limits
Z.AI answers each limit of its GLM Coding Plan in the same way as a rate limit. Squad says which limit it was, in chat and on the card for work that did not finish on Today and Needs you:
On Telegram and Slack, the teammate’s reply is the same sentence, after “⚠️”. Squad for Mac shows the same sentences.
A usage limit that Z.AI reports with “Insufficient balance for extra usage” is a used-up usage limit, not an account out of credits. Your plan’s limit comes back by itself.
Time limits
Squad does not stop a run because it takes a long time. In Settings > AI, under More, the Run time limit card says “Runs have no time limit.” and shows No limit. You cannot set a time limit. Each routine that you create in the dashboard gets 24 hours, and the routine editor has no time limit field. A run can still stop for one of these reasons:- It showed no progress for 15 minutes. Squad stops a run that sends no progress signal, such as a tool call, for that period. Squad does not stop a run while a tool call or a memory compaction is in progress, but it ends a tool call that makes no progress (see below). Runs on a Claude Code account are not stopped this way. See Limits and defaults.
- A time limit from an earlier setting is still saved. Runs that take longer than that limit are stopped, even while they are still working. If the squad has no saved value, the card shows 10 minutes, and chat runs stop after 10 minutes.
- A routine that a teammate created another way than through Routines, for example before October 19, 2026, can have no time limit saved. Its runs then stop after 60 minutes. A routine that a teammate creates now gets 24 hours unless you ask for less. To raise the limit now, select Raise to 24 hours in the routine’s editor, then Save changes. Your cloud computer also raises it the next time it restarts.
1
Open the run
Open the run detail with the label Ran out of time.
2
Open the limit
Select Check the time limit. For a routine’s run, the teammate’s Setup opens with the editor of that routine. For other runs, AI opens with More open.
3
Routine runs
The editor says “This routine stops after [time].” Select Raise to 24 hours, then select Save changes.
4
Other runs
The Run time limit card shows the limit and says “This limit comes from an earlier setting. Runs longer than it are stopped even while they are still working. Remove it, then save.” Select Remove the limit. Then select Save changes in the bar at the bottom.
Interrupted runs
A restart of your cloud computer ends every run in progress. Saving settings does not restart it. The cloud computer restarts for new software that it can load only when it starts, and that restart waits until no teammate is working, also on a Claude Code account, with no time limit. It restarts at once when it stopped answering and Squad recovers it. On a cloud computer that does not have the update for saves without a restart yet, a save can still restart it, and the screen then says that it is still restarting. See Limits and defaults. The run detail shows Interrupted. Unless Squad continued the run as described below, it says “Routine maintenance interrupted this run before it finished. It is not run again, so check that its work got done.” When a program that a teammate runs, for example a video edit, uses up the memory of your cloud computer, only that program is stopped. The run goes on, and the teammate learns that the program failed. The cloud computer does not restart, and other teammates keep working. A run on a Claude Code account also waits for free memory before it starts. See A teammate says “Waiting for memory to free up on the cloud computer”.A chat message in the dashboard
When it can, Squad gives a chat message that a restart interrupted back to the teammate on its own. The chat then shows “[name] was interrupted by a restart and is picking up where it left off.” The teammate continues in the same conversation, sees what it already did, and is told not to repeat an action that already completed, such as a sent email. Squad does this a limited number of times for one message. See Limits and defaults. When someone wrote to the teammate from a chat app, such as Telegram or Slack, after you sent the message, the teammate reads that conversation before it goes on. If that conversation stops or changes your request, the teammate does what it asks instead and says so in its reply in the dashboard. When the message reaches the teammate again, the run that the restart cut off shows “A restart cut this run short, and Squad picked it back up.” in History, and its row on Health is tagged resumed. The continued work is a new run. You do not need to send the message again. Squad does not continue a message that you stopped, edited, or reset, or a message that it cannot continue safely. The chat then shows “Your cloud computer restarted while handling this message, so it may not have been processed. Send it again if nothing arrived.” Check the work, then send the message again if it is not done.Other work that a restart cut off
About 2 minutes after a restart, Squad wakes each teammate that the restart cut off, so that it picks its work back up. This covers:- Work on a task, and a mention or another request that woke the teammate.
- A reply that the teammate was writing in Telegram, Discord, Slack, or another chat app. The teammate finishes the reply in that chat. When it cannot tell what was asked, it says in that chat that its answer was cut off by a restart and asks you to send your message again.
- A routine’s run. The teammate finishes the run and sends its result where the routine reports.
- The teammate is paused, or your squad cannot work, for example because it is locked or its computer is being moved.
- You paused or deleted the routine after the run started.
- The same work already ran again, for example the routine ran at its next time, or you wrote in the same chat.
- A person wrote to the teammate since the run started, in any conversation, in the dashboard or from a chat app such as Telegram, Slack, or Discord.
- Every task that the work was for is done, archived, or deleted.
Ask the teammate
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, except a Claude Code usage limit that switches to your next account (see above)
- A rate limit when you set no models to try next. A rate limit never switches Claude Code accounts.
- A model that Google refuses because your Google AI key is on Google’s free plan. The run moves to the next model at once.
- A run where all models in the list failed
- A chat reply that failed. Select Retry yourself.
- A manual run or a chat run that failed with a provider error
- A heartbeat, a trigger’s run, or a helper’s run that a restart interrupted
A task shows “Stuck for … · no progress”
Symptom: a task card on Tasks shows “Stuck for” a time, then “no progress”. Cause: the task had no update for a long time. The teammate can be waiting for your answer, or its runs can be failing. Fix:- Open Needs you and answer any open question for that task. See Answer what needs you.
- Check Today for a card about that teammate’s work that did not finish.
- Open the task and select Ask and the teammate’s name for an update. See Ask for an update.
A teammate says “Waiting for memory to free up on the cloud computer”
A teammate on a Claude Code account needs free memory on your cloud computer before its run starts. When several Claude Code runs start at about the same time, a run can wait. After 15 seconds of waiting, the teammate’s line in the sidebar and its working message in chat say “Waiting for memory to free up on the cloud computer”. Until your cloud computer has its next update, the line can still say “Waiting for other work on the cloud computer to finish”. The run already shows Running. Cause: your cloud computer has too little free memory while other Claude Code runs work. Teammates on other AI accounts do not wait this way. Fix: wait. The run starts by itself when memory frees up, for example when another Claude Code run ends, and the line goes away. The wait has no time limit and does not fail. To make room sooner, stop a run that you do not need. See Stop a run. For the numbers, see Limits and defaults. When teammates keep waiting, a banner says so. See Your cloud computer keeps running low on memory.A teammate shows “Paused”
Symptom: the teammate’s page shows “Paused by” and a name, “Paused”, or “Paused ·” and a reason, at the top. Its routines do not run, and a chat message to it fails with “[name] is paused. Resume [name] to send a message.” Cause: you, an Administrator, your chief of staff, or the teammate itself paused the teammate. The page names who paused it (right after you pause it yourself, Paused by you). A pause from before September 30, 2026 shows only “Paused”. A paused teammate does not start new work from the dashboard. Its routines and its Native heartbeat are off, the dashboard does not send it chat messages, and group chats do not wake it. @mentions, task assignments, and emails for the teammate wait until it is resumed. Messages from Telegram, Discord, or Slack still reach it. Fix: select Resume, or ask your chief of staff to resume the teammate. The teammate then gets the @mentions, task assignments, and emails that waited. For more, see Add, change, and pause teammates. If the page says “[name] needs attention.” and a reason, read the reason and follow the fix on this page.A new teammate does not answer yet
Symptom: your chief of staff just added a teammate. 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 teammate 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 teammate can go to the chief of staff instead.A teammate works on the wrong thing
Symptom: a teammate started work that you did not want, or a run takes a wrong turn. Cause: the teammate understood the message differently than you meant, or it chose a path that you did not expect. A run goes on until it finishes unless someone stops it. Fix: stop the run. In chat, select Stop under the teammate’s working message. In History, select Stop on the run’s row. Then select Stop the run. You must be the owner or an Administrator. The run shows Stopped, and Squad does not count it as a failure. Then tell the teammate what you want instead. See Stop a run. If Stop says “The stop didn’t go through, so the run is still going. Press Stop to try again.”, select Stop again. If it says “Your cloud computer hasn’t confirmed the stop yet. If the run keeps going, press Stop again.”, the run may still stop. Select Stop again only if the run keeps going. If Stop says “Your cloud computer needs an update before Stop works. It updates on its own, so try again later.”, wait and try again later.Ask your chief of staff to check
Your chief of staff can look at the problem from inside your squad.Ask your chief of staff