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, and this page is available as Markdown at https://www.jumpserver.com/docs/features/audits/jobs/job-executions.md.
๐ŸŽ‰ JumpServer v5.1.1 is available. See what's new โ†’

Job Executions

Job Executions records each run of a job created in the Workbench Job Center. Use it to confirm that scheduled jobs ran, to find failed runs, and to inspect the execution output for troubleshooting.

Open the page from Audits > Job Audits > Job Executions.

Overview

Each row shows the creator, command, job type, completion state, success state, duration, start date, and available actions. A running job shows a spinner in columns that are not final yet. Failed runs are marked with a red cross and successful runs with a green check.

The toolbar provides search, a date range, column settings, export, and refresh.

Prerequisites

  • Sign in with an account that has the audits.view_joblog permission, such as a system administrator or auditor.
  • A quick command or job must have been executed from the Workbench Job Center.

Review executions

1

Set the date range to the period you want to review.

2

Search for a creator or command to narrow the list.

3

Click View in the row actions to open the execution output.

4

For a running job, click Stop to terminate it when it should no longer run.

Figure 1: Job Executions list with creator, command, job type, completion, success, duration, and start date.

Warning

Stop terminates a running job and may leave part of its work unfinished. Use it only when the job must be interrupted, and tell the job owner afterward.

Customize columns and export

Open List preferences, select the columns to display, and click Confirm. Extra columns include ID and completion date. Restore defaults resets the list.

Figure 2: List preferences for job executions.

Click Export, choose CSV or Excel, select Export all, Export selected, or Export search results, and click Confirm.

Field reference

FieldDescription
CreatorUser who triggered the execution.
CommandCommand or playbook material that was run.
Job typeType of job that produced the execution.
FinishedWhether the execution has finished.
SuccessWhether the execution completed successfully. Shows a spinner while running.
DurationElapsed time of the execution, in seconds.
Start dateWhen the execution started.
ActionsView opens the output; Stop terminates a running job.
Completion dateOptional. When the execution finished.

Notes

Tip

For failed runs, open the output first and then check the job definition in Job Audits to see whether the failure came from the command, the target assets, or the account.