> For AI agents: the complete documentation index is available at https://www.jumpserver.com/docs/llms.txt, the full documentation bundle is available at https://www.jumpserver.com/docs/llms-full.txt.

# Execution History

**Execution History** records the Job Center tasks you started. Use it to trace
what a batch operation ran, whether it finished, whether it succeeded, and how
long it took. When a bulk command or job returns an unexpected result, this page
is the first place to check.

![Figure 1: The Execution History page](/images/v5/jumpserver/v5_admin_wb_hist_01.png)

## Prerequisites

- The **Job Center** feature is enabled in
  [Feature Settings](https://www.jumpserver.com/docs/features/system-settings/general/features.md).
- Your role grants access to execution records.
- You have already run an Adhoc command or a job. The list is empty before the
  first execution, and it only shows executions you started yourself.

## Inspect an execution


1

Open **Job Center > Execution History** in the Workbench.

2

Use the search box to find a command or task, and sort by the column headers to
bring the newest or slowest run to the top.

3

Click the **Output** action in the row to open the task page with the full log of
that execution.

Column settings control which fields are visible, and the refresh icon reloads the
list after a run finishes.

## Column reference

| Column       | Description                                                                          |
| ------------ | ------------------------------------------------------------------------------------ |
| Command      | Command that was executed, for example the command text or job content               |
| Job type     | Type of the run, such as Adhoc, Playbook, or Upload File                             |
| Is finished  | Whether the task reached a final state                                               |
| Is success   | Whether the task completed without errors. A spinner means the task is still running |
| Duration     | Time used by the execution                                                           |
| Date created | When the execution was created                                                       |
| Actions      | **Output** opens the execution log                                                   |

## What appears here

Executions come from actions that use the Job Center execution channel, including
Adhoc commands, saved jobs, and file transfers. Because only your own executions
are listed, another user's runs never appear on this page. For a complete,
audit-oriented view, auditors use
[Job Audits](https://www.jumpserver.com/docs/features/audits/jobs/job-audits.md) and
[Job Executions](https://www.jumpserver.com/docs/features/audits/jobs/job-executions.md), which are available from
the Audits module.


Note

An execution is created when the run starts, not when it is scheduled. A periodic
job that has never run has no history entry, and a currently running task shows an
incomplete result until it finishes.


Tip

Compare the **Duration** column with previous runs of the same command. A sudden
increase often points to an unreachable asset, a slow network path, or a job that
is waiting on a timeout.