Find a run
1
Open Runs
Open Runs.
2
Pick a view
Pick a view: Day, Week, Month, or Schedule. Schedule is the default. It shows UPCOMING scheduled runs and the runs of the last 3 days. Day shows one day. Week shows 7 days, and today is the last column. Month shows the current month up to today. Click a day in Month to open it in Day.
3
Set the filters
In the FILTERS panel, choose what to show:
- AGENTS: turn agents on or off.
- ACTIVITY: Scheduled runs, Manual runs, Chat, Emails, Research, Integrations, Tool calls, Triggers.
- SCHEDULES: All schedules or one schedule.
4
Move through the days
Use Previous, Next, and Today to move through the days. In Week, Previous and Next move 7 days at a time. Month always shows the current month. In Schedule, click Load older runs to go back further.
Read a run’s detail
Click a row. The detail panel shows:- SUMMARY and, for research runs, PARAMETERS and RESULT PREVIEW
- WHAT IT TOUCHED, and REQUEST and RESPONSE where they apply
- USAGE: Input tokens, Output tokens, Cache read tokens, and Cache write tokens
- SKILLS USED
- View related mission when the run belongs to a mission
- Technical details, with the Model, Provider, Reasoning level, and Channel.
See subagent runs
When an agent hands part of a job to a subagent, the subagent’s run is its own row in Runs:- Its kind is Subagent, and its title is “Subagent:” followed by its label. When Squad has no details of the subagent, the title is “Subagent run”.
- It sits indented under the run that started it. When that run is on another day, the row says Started by and the agent’s name.
- Its detail shows who started it. When Squad has them, it also shows the full task, Open the run that started it, and Open the chat. The run that started it must be in the days that you are viewing for Open the run that started it to show.
- The detail of a run that started subagents lists them under SUBAGENTS.
- The Subagents filter appears when the list has a subagent run.
See trigger runs
A run that a trigger started is its own row in Runs:- Its kind is Trigger, and its title is “Webhook:” or “App event:” followed by the trigger’s name.
- One run can carry several events that arrived while the trigger’s last run was going.
- On the trigger’s page, Open in Runs on an event opens its run here.
Stop a run
Stop a run when an agent works on something that you did not mean to start, or takes a wrong turn. Before you start: you must be the owner or an Administrator. Collaborators and Viewers do not see Stop. An Administrator who is limited to some agents cannot stop the runs of the other agents. Stop is in three places:- In chat, under the agent’s working message. See Stop a reply in progress.
- In Runs, on the row of a run that shows Running. Research and tool call rows have no Stop.
- In the detail panel of a run that shows Running.
1
Select Stop
Select Stop. Its tooltip says “Stop [agent]‘s run. Anything it already saved stays.”
2
Confirm
Select Stop the run. To let the run continue, select Keep going.
3
Wait for the run to end
Stopping… shows until the run ends.
- Your squad’s computer stops the run and the helper agents that it started. Work that the run already did stays. For example, a saved file, a sent email, or a created mission is not undone.
- The run shows Stopped. Squad does not count it as a failure. You get no failure notification, Squad does not run it again, it is not on Health, and it does not lower Success rate.
- A run that finished before the stop arrived stays Completed.
- The agent keeps the conversation. With your next message, it knows that the last run was stopped.
When the stop does not go through
Check today’s problems on Health
The Health screen has no menu entry. You open it from these one-line links:
The Health screen shows today’s runs only. Its sections are:
- All clear: “No failed or interrupted runs today, and no provider limits in effect.”
- PROVIDER STATUS: an AI provider is rate-limiting your agents. See Choose models and manage AI accounts.
- NEEDS A LOOK: each failed run, with the agent, the trigger, the time, the error, Technical details, and View in Runs →.
- ROUTINE INTERRUPTIONS: runs that maintenance, a restart, or a provider error interrupted. Each row is tagged resumed or not run again. When every row is resumed, the section says “Routine events interrupted these runs, and each one resumed automatically, so nothing is needed from you.”
Know when Squad resumes a failed scheduled run
When a scheduled run fails because the AI provider had a temporary problem, Squad wakes the agent once more, two minutes later. The agent is told to check where it left off, finish the remaining work, and not redo steps that already succeeded.
A resumed run shows “A model-provider hiccup interrupted this run; resumed automatically.” in Runs and in its detail. A chat run that a restart cut off and that Squad continued shows “A restart interrupted this run; Squad resumed it automatically.” instead. See Interrupted runs. It is listed under ROUTINE INTERRUPTIONS on Health, and it does not lower the agent’s Success rate.
Squad does not resume a run that failed with a rate-limit error. See Choose models and manage AI accounts.
Follow the Live Feed
The Live Feed lists what your squad does, newest first. It shows today’s items. If there is nothing today, it shows older items.- While you were away sums up the events since your last visit, by agent, with the number of blocked items.
- PREVIOUSLY SEEN marks where your last visit ended.
- Filter by agent with All agents or an agent’s name, and by type with All activity, Missions, Needs you, or Updates.
- Click an item to open its mission. An item without a mission opens its activity page, where you can read the detail and add a comment.
- Click Load older activity → to see more.
Check that it works
- A run that you just started shows as Running in Runs, then Completed.
- A run that you stopped shows Stopped.
- Health shows All clear when nothing failed today.
- The Live Feed shows your agents’ latest actions at the top.