Execution history

Monitoring execution records of all jobs; examining error, step, tenant result, and console output in the detail window.

Execution history screen collects execution records of all jobs in the scheduler into a single list. You can see which job started when, how long it lasted, whether it was successful, and the error message if it failed. Each record's Detail window contains the step-by-step progress of the execution, tenant-based results, and console output. This screen is used by operations and support teams investigating errors in background jobs.

Accessing the screen

Follow the menu path Scheduler › Execution history. Execution history is also available as a shortcut under the Scheduler card in the product launcher. Access to this screen is separate from the Jobs screen; if you do not see it in the menu, your account does not have permission for this screen.

If you want to see executions of only a single job, click the job name on the Jobs screen and use the Execution history tab on the detail page. The Detail button there opens the same window as on this screen.

Screen sections

• Title: Execution history.
• Filter area: There is no filter area on this screen; only Clear and Filter buttons are visible. Filter reloads the list from the first page.
• List toolbar: Per page selection, "Filter result: N records" info, refresh button, and Columns menu.
• List: one execution per row; Detail button at the right end of the row.
• Pagination: record range shown below the list (e.g. "1–25 / 300"), page info in "Page 1 / 12" format, and previous/next page arrows.
• Execution detail window: opened by the Detail button.

List

Durations are shown in a readable format: under one second as milliseconds ("850 ms"), under one minute as seconds ("1.2 s"), longer durations as minutes and seconds ("2 min 5 s").

• Page size: You can select 25, 50, or 100 records per page from Per page; default is 25.
• Sorting: Column headers do not sort; the list is shown in the order received.
• Columns: You can hide or show columns other than Job from the Columns menu. Your selection is saved in your browser.
• Row click: Clicking a row does nothing; use the Detail button at the end of the row for details. The job name in the Job column is not a link on this screen.
• Refresh: The rotating arrow icon in the toolbar reloads the list. The list does not update automatically; refresh to see the result of an ongoing execution.

Actions

Viewing execution details

Use this to understand why an execution failed, which step got stuck, or which tenants had issues.

1. Click the Detail button at the end of the relevant row.
2. Review the information from top to bottom in the opened Execution detail window (see the section below).
3. Click Close when finished.

This screen does not allow restarting, stopping, or deleting executions. To rerun a job, use the Run now button on the Jobs screen.

Execution detail window

The window title is Execution detail, with the job name and execution ID below. The content consists of the following sections from top to bottom:

Summary line

Status badge and these fields:

If the execution failed, the error message is shown immediately below the summary line in a red box.

Tenant results

Visible only if tenant-based results exist. Each tenant has a separate row:

If you see a value like "8/10" in the Tenant column in the list, you can find the two failed tenants in this table by their Status and Technical detail columns.

Steps

Shows the steps inside the execution in order. If a step has sub-steps, they are listed indented on a sub-row, showing which step is part of which. Each step row shows:

• step status badge (Pending, Running, Successful, Failed, Skipped),
• step name,
• if progress is tracked, processed / total count (e.g. "120/500"),
• step duration on the right,
• step message below if available.

If no step info exists, it shows "No records found".

Console

Shows log lines produced during execution in fixed-width font. Each line includes time, level, and message. This section shows the first 500 lines from the start and scrolls internally for long outputs. If output exceeds 500 lines, the remainder is not visible and no warning is shown; if the last lines are missing, consider the output may be truncated. If no console output exists, it shows "No records found".

Tip: When investigating an error, first check the red error box, then the step with the Failed badge and its message in the Steps section. If needed, examine console lines near that step's time in the Console section.

The window does not update automatically while open. The status and duration in the summary line reflect the info at the moment you opened the window. To monitor progress of a Running execution, close the window, refresh the list, and reopen after some time.

Statuses

Execution statuses

Step statuses

Common situations

• Execution history not in menu but Jobs is. Access to this screen is separate. You can see a single job's history on the job detail page's Execution history tab; contact your system administrator for access to this screen.
• I want to find executions of a specific job. There is no filter on this screen. For a job's own history, search and click the job name on the Jobs screen and open the Execution history tab.
• The list is empty. No execution records exist yet or data could not be retrieved. Click the refresh button. If "Something went wrong" appears, use the Retry button; if the problem persists, send the Technical detail text to your system administrator.
• Steps or Console say "No records found" in the detail window. No step or log lines may have been produced for this execution; the window also shows this message if data could not be retrieved. To be sure, close and reopen the window after a while. Trace the error cause from the error box below the summary line and the Steps section.
• Tenant column shows "—". The execution did not produce tenant-based results; the job is not multi-tenant or tenant count was not recorded.

Related screens

• Jobs
• Overview
• Using list screens