Skip to content

Work History in XTM One

History is where you review what agents have already done. It is the operational record for runs, waiting items, notifications, and failures.

What Work History is for

Use History when you want to:

  • check whether a task is still running
  • review a completed result
  • respond to a request for human input
  • isolate notifications or digests
  • follow work that moved between agents

Open History

Choose History from the left sidebar.

The main page shows runs across your visible agents. It is designed for filtering first and investigation second.

Use the main filter tabs

At the top of the page, XTM One provides quick filter tabs.

You can switch between:

  • All
  • Notifications
  • Digests
  • Running
  • Awaiting Input
  • Completed
  • Failed

These tabs are the fastest way to narrow the page to the type of work you care about.

Use the other filters

In addition to the main tabs, you can refine the list with:

  • search
  • ownership
  • agent selection

Ownership usually includes:

  • All
  • My Runs
  • Shared Runs

This is useful when you work in a shared environment and only want to focus on your own workload or on cross-team runs.

Understand the run cards

Each run card gives you a quick status summary.

You may see:

  • the agent name
  • the assignment or run title
  • a short summary
  • the current state
  • the creation time
  • delegation indicators

Typical states include:

  • running
  • awaiting human input
  • completed
  • failed

Notifications and digests

The Notifications and Digests filters are there for communication-oriented runs.

Use them when you want to:

  • review automated updates sent by the platform
  • separate digest-style outputs from normal task runs
  • find communication outputs without scanning every run

When a run is waiting for you

Some runs pause and ask for human input.

When that happens:

  • the run appears under Awaiting Input
  • the run detail page shows the question or pending action
  • you can respond directly from the run
  • you can dismiss the waiting item if it is no longer needed

This is the main place where human approval or clarification appears in the UI.

Open a run detail page

Click any run to open the detailed view.

The run detail page usually includes:

  • the run title
  • the status
  • the agent
  • the trigger that started the run
  • timestamps for created, started, and completed states
  • shortcuts to the related agent, assignment, or parent run

Review the result

For completed runs, the detail page helps you understand what happened.

Depending on the run, you may see:

  • a final summary
  • tool actions
  • intermediate reasoning or step history
  • output sent to another system
  • child runs created through delegation

This makes the page useful both for everyday checking and for troubleshooting.

Follow delegated work

One run can create more runs if work is handed to another agent.

Use the history list and the detail page together to understand:

  • where the work started
  • whether another agent took over
  • which parts succeeded or failed

This is especially important in environments that use multi-agent flows.

Bulk actions

The history page also supports selection and cleanup actions.

Depending on your permissions, you may be able to:

  • select multiple visible runs
  • delete selected runs
  • select all runs matching the current filters

Bulk actions are useful when you need to clean up large sets of test runs or old operational records.

Administrator-only cleanup

Administrators can also see Cleanup Stale Runs.

This action is meant for recovery situations, such as:

  • a restart left some runs stuck
  • a run exceeded its timeout
  • the page still shows work as running when it should have failed

The cleanup action marks those stale runs as failed so the history becomes accurate again.

Next step

The next chapter covers Resources, which includes knowledge bases, prompts, skills, MCP servers, tools, variables, and integrations.