---
title: Details tab
description: See which agent and version ran, when the run started and finished,
  and the input, result, and metadata it recorded.
editUrl: true
head: []
template: doc
sidebar:
  hidden: false
  attrs: {}
pagefind: true
draft: false
---

The run as a whole, without the span-by-span breakdown: which agent and version ran it, its lifecycle timestamps, and any input, result, and metadata recorded for it.

![The Details tab of a failed run, listing the agent, status, and timestamps.](../../../../assets/screenshots/web-app/instance-details-tab.png)

For what sits above the tab row, see the [Agent instance page](/web-app/agent-instance).

## Details

- Agent — the agent that ran the instance, linked to its [Agent page](/web-app/agent).
- Status — the current lifecycle state. A Terminated run also shows the reason given when it was terminated.
- Created — when Prefactor first recorded the instance.
- Last updated — when Prefactor last saw a change to the instance.
- Started — when execution began. Only shown once the run has started.
- Finished — when execution ended. Only shown once the run has finished.
- Agent version — the version that ran the instance, linked to that version on the [Agent page › Configuration tab](/web-app/agent/configuration). Versions that run hosted carry a "(Hosted)" suffix.

## Input, result, and metadata

Below the fields, each payload the instance recorded has its own section: the input from when the run was registered, the result from when it finished, and the run's metadata. A section only appears when the instance has that payload.

A section's heading and description come from the schema the payload was recorded against. Without a schema title, the headings are "Input parameters", "Recorded result", and "Metadata". Each row is one field: the schema's title for the field, or the raw key when it has no title, with the field's description beneath it and its value alongside. Rows are in alphabetical order by key. Dates show in your timezone, long text can render as formatted text, and objects and arrays appear as formatted JSON. A judge's verdict shows as a pass or fail badge.

When the metadata schema has a template, its summary appears in the strip above the tabs.

Sensitive values in the payloads are redacted. When an instance has any, **Show sensitive information for this instance** appears in the strip above the tabs. Selecting it reveals them on this tab until you change tab. Discarding an instance's sensitive values is done through the API.

To record these payloads for your own agent, see [Record a run's input, result, and metadata](/api/instance-payloads).

## Related

- [Instance](/platform/concepts/instance#input-result-and-metadata) — what an instance record contains and how its lifecycle works.
- [Agent instance page](/web-app/agent-instance) — the strip above the tabs.
- [Agent instance page › Activity tab](/web-app/agent-instance/activity) — the span-by-span view of the run.