> ## Documentation Index
> Fetch the complete documentation index at: https://docs.meetsquad.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Run history

> Every time an agent ran, what it changed, and what it produced. How to read a run row and what its status actually means.

**Run History** sits at the bottom of every agent's detail page. It lists the agent's runs, newest first, up to the 50 most recent. Before the first run it says so and tells you runs appear once the agent is scheduled or run manually.

Each run is one collapsed row. Click it to expand.

## Statuses

Six statuses, each with its own badge.

<AccordionGroup>
  <Accordion title="Pending" icon="clock">
    The run exists and is queued. Nothing has started.
  </Accordion>

  <Accordion title="Running" icon="loader">
    In flight, with a spinner.
  </Accordion>

  <Accordion title="Success" icon="circle-check">
    Finished and did its work.
  </Accordion>

  <Accordion title="Partial" icon="circle-alert">
    The run did its work, but something downstream failed. A Slack delivery that could not post is the usual cause. The output exists. The last mile did not complete.
  </Accordion>

  <Accordion title="No change" icon="minus">
    A success. The agent ran, looked, and found nothing worth acting on, so it produced nothing. The label reads like a problem and is not one. A daily competitor watcher will show plenty of these, and that is the correct outcome for a quiet day.

    <Tip>
      If you want a report even on those days, turn on **Report when nothing changed** in the agent's report settings.
    </Tip>
  </Accordion>

  <Accordion title="Failed" icon="circle-x">
    The run itself broke. The error is in the expanded row.
  </Accordion>
</AccordionGroup>

## The collapsed row

Left to right, a row carries the status badge, what started the run (a scheduled run, a manual run, or an event run), and a line of facts underneath:

* Whether content changed: changed, no content change, or sources unavailable. Sources unavailable means the run proceeded but every source it tried failed to load, which is different from genuinely finding nothing new.
* How many signals the run created.
* How many documents it touched.
* **Report**, when the run produced one.
* The event and entity that fired it, on event-driven runs.
* A per-source tally, on runs with sources: how many were read and how many failed.

On the right sits the duration and when it ran, as both a relative time and a date. Runs that produced a report also get an **Open report** button on the row when the window is wide enough.

## The expanded row

Expanding a run gives you, in order:

<Steps>
  <Step title="The error" icon="circle-x">
    In a red panel, if the run recorded one.
  </Step>

  <Step title="Summary" icon="file-text">
    Shown when the run wrote a report. The report's title and its summary, rendered, plus the token count and model that produced it, and an **Open report** button.
  </Step>

  <Step title="Documents and insights" icon="files">
    A list of the documents and insights this run created or updated, each labelled created or updated and linking to the thing itself.
  </Step>

  <Step title="Audit trail" icon="list-checks">
    A compact table of what the agent did during the run. Click any line to open its detail. A run with nothing recorded says so.
  </Step>
</Steps>

<Warning>
  The counts on the collapsed row are authoritative. The **Documents and insights** list and the **Audit trail** are best effort.

  Both are built from the activity that has been loaded for this agent, which arrives a page at a time. A long run can list fewer entities than the same row's count claims, and its audit trail can be short of everything that happened. When the two disagree, believe the counts.
</Warning>

There are no per-tool-call timings. A run reports its total duration. The audit trail records what the agent did, not how long each step took.

## Where reports go

Every report an agent writes is saved to the system **Agent Reports** folder, whether or not you set up delivery. It is a normal document from there: searchable, editable, and versioned.

Delivery adds copies. Two channels ship: a **Slack** channel, once Slack is connected, and **Email** to selected org members. Knowledge and insights are not delivery channels. The **Gain knowledge** and **Discover insights** outputs on the agent already handle those, so routing a report through them as well would duplicate the same work.

Open a report from the run row, from the **Latest Report** card in the agent sidebar, or from the Agent Reports folder in your [knowledge base](/knowledge-documents).

## Reading a problem

<AccordionGroup>
  <Accordion title="The agent is in error" icon="triangle-alert">
    Expand the newest run and read the message. Fix the cause, then **Resume** from the agent header. Agents in error do not restart themselves, which stops a broken source being hammered.
  </Accordion>

  <Accordion title="Every run says sources unavailable" icon="unplug">
    The pages or channels the agent reads are failing. Check the per-source tally on the row, then check those entries in [Tools and access](/agent-tools-access). A URL that moved needs replacing. A Slack channel the bot was removed from needs the bot back.
  </Accordion>

  <Accordion title="A run succeeded but nothing arrived in Slack" icon="message-square-off">
    That is what **Partial** means. The work is done and the report is in Agent Reports. Check the report's delivery status, fix the channel, and redeliver from the report.
  </Accordion>

  <Accordion title="Run now is greyed out" icon="ban">
    The agent is paused, in error, or already running. One run at a time per agent, always.
  </Accordion>
</AccordionGroup>