Track agent runs
Activity lists every agent task in your team, in one place you can open from anywhere: select Activity in the action bar, on any page. Use it to see what is under way, read what an agent produced, answer a question an agent has paused to ask, and stop or clear a run.
Where runs come from
A run reaches Activity in one of three ways:
- you dispatched it from Workflows;
- you sent documents to a workflow or an extraction schema from the documents table — see Work with the documents table;
- a policy fired and dispatched it for you — see Create and manage policies.
A help banner at the top says the same thing. Dismiss it once you no longer need it.
Activity also records documents the AI has saved from your discussions — see Documents saved from discussions below — your team's flying minutes work, drafting passes and document generations alike — see Flying minutes activity — and every document generated from a template — see Template generations.
Wherever you dispatch a run from, the confirmation message carries a View link that brings you straight here. Workflows and extraction schemas also carry a View runs control that opens Activity showing just that one's runs — a "Scoped to" chip in the toolbar says so, and dismissing it brings back everything.
While work is under way, the Activity button itself shows a count of runs in flight — amber when an agent is waiting on someone's answer.
Read the list
Each row is one run, whichever way it was set going.
| Column | What it shows |
|---|---|
| Trigger | A pill reading Workflow, Extraction, Build, Policy, Discussion, Minutes drafting, Minutes generation, or Template generation, and the name of the one behind the run. |
| Status | An icon for where the run has got to. See below. |
| Created | How long ago the run was created. |
| Duration | How long the run has taken. |
| Actions | Cancel, for a run still going; dismiss, for one of your own that has finished. |
The Status icons are:
- a spinner — the run is waiting to start, or is under way;
- a green tick — the run finished;
- a red cross — the run failed, timed out, or was cancelled;
- a pulsing amber Needs input badge — the agent has paused to ask you something. Select the badge to answer; see Respond to an agent request.
Narrow the list
The toolbar filters the list however you need:
- search by name;
- the type pills — select one or more to see only runs of those kinds;
- a status filter offering All, Active, Completed, and Failed;
- Mine only, to hide your teammates' runs;
- a date range.
The list pages through long histories; the footer shows where you are. When nothing matches, it says "No activity matches the current filters."
Open a run
Select a row and the run opens in its own window: the run's name and status at the top, and its results below.
- A completed extraction run shows its results grid — one row per item, with sources and notes — then Notes from the extracting agent where the agent had something to add about the documents, a Reports section, and export controls. This window is the only place the grid appears; the Extractions page is where schemas are written and run, not where results are read. See Extract information from contracts.
- Any other completed run shows its output.
- A run that has paused shows the agent's question, with a Respond button.
- A footer line holds technical details, which you can quote to support if you need to raise the run with us.
Keep a run's output
A completed workflow or extraction run carries a Save to documents button at the top of its window. Select it and a window proposes a title for the new document, which you can change, and lists your team's collections with the ones the run's documents belong to already ticked. Select Save and the run's results are saved as a new document in your team's library — an extraction run as a results table, any other run as its output — and filed in the ticked collections. A confirmation says where it went and carries a View link that opens the new document.
Once saved, the results behave like any other document: you can search them, share them, discuss them, and send them to further workflows. The document records which run it came from, and is linked to the documents the run analysed, so it appears alongside them.
Saving again creates a second copy — useful if you want to keep a snapshot before dismissing the run. Runs fired by a policy, and runs that failed or are still going, cannot be saved.
Some runs also produce attachments — extra outputs the agent set aside while it worked, such as a table, a draft section, or a rendered file. They appear in their own section when you open the run. Expand a text attachment to read it in place, or download a file attachment. Each attachment has its own Save to documents button: a text attachment becomes a document straight away, while a file is added to your library and processed like any upload, appearing on the Documents page shortly after.
Reports produced from an extraction run appear under Reports rather than among the attachments, because they are made from the run's results after it finished rather than set aside during it. They behave the same way: open a report to read it, and use its own Save to documents to keep it. See Reports.
Documents saved from discussions
When you ask the AI in Discussions to save something as a document, the save is recorded here too: a row with a Discussion pill, named after the document it created. Only you see these rows — they belong to your discussion, which is private to you — though the document itself sits in the team's library like any other.
Open the row and it offers two links: View document opens the document, and Open discussion takes you back to the conversation that produced it. There is nothing to cancel or dismiss — the save has already happened. The row disappears if you delete the discussion, or if the document is moved to the trash.
These rows do not count towards the number on the Activity button; they simply appear in the list the next time you open it.
Flying minutes activity
Each time someone uses Automatically draft or Prepare for Download in Flying minutes, that piece of work is recorded here as its own row — a Minutes drafting or Minutes generation pill, named after the session. Everyone on your team sees these rows, just as everyone sees the team's sessions on the Flying minutes page.
A row shows as running while the work is under way, then completed — or failed, with the reason shown when you open the row. Repeat generations each get their own row, so a session's full history stays visible. Open a row and select Open session to go to the session itself; that is where the draft, the form, and the download live. There is nothing to cancel or dismiss, and if the session is deleted its rows leave the list with it.
Template generations
Each time someone generates a document from a template, the generation is recorded here as its own row — a Template generation pill, named after the template. Everyone on your team sees these rows.
A row shows as running while the documents are being prepared, then completed — or failed, with the reason shown when you open the row. Generating again creates another row, so a template's history stays visible. Open a row and select Open template to go to the template on the Workflows page's Templates tab; its Documents table is where the generated files live. There is nothing to cancel or dismiss, and if the template is deleted its rows leave the list with it.
Cancel a run that is still going
A run that is waiting to start, under way, or paused for input carries a cancel action in its Actions cell. Select it and confirm. The confirmation warns you that the agent will be stopped and any work in progress lost. The run's status then changes to cancelled.
A run that has already finished has no cancel action. Nor does a run a policy fired — those cannot be cancelled at any point.
Dismiss a run you have finished with
Once a run has finished — whether it completed, failed, timed out, or was cancelled — a trash action appears in place of cancel. It appears only on runs you dispatched yourself. Select it and confirm. The run disappears from the list, and from anywhere else it was shown, and it does not come back.
A colleague's run has no trash action for you. It stays in the list until whoever dispatched it dismisses it; once they do, it disappears for the whole team.