# Job Execution History

Every time a job fires an import or an export, all the logs get stored in the “**Job Execution History**” module. Within these logs, users can find detailed information such as the job's status, execution results, details about exported files, and the scheduled time and date for the next execution.

Regular analysis of the execution logs can help review job performance and find potential bottlenecks. The job execution history module allows users to identify patterns of errors or warnings, detect jobs with extended run times indicative of potential performance issues, and make informed decisions such as re-running or halting job executions.

### Selecting the Job

To view the job execution history, you will begin by selecting the job. By default, the Job Execution History module displays the activity history of all the jobs created in the system. However, you can select a job from the "Select Job" dropdown to view the execution history of a particular job.

<figure><img src="/files/bxK0ZqKYdvOqGBgZVWik" alt=""><figcaption></figcaption></figure>

### Understanding the Logs

Once the job is selected, the activity logs of the execution history will be displayed. The logs provide detailed information including job execution time, status, messages, and job statistics.

#### **Logs Fields**

<table><thead><tr><th width="187">Field</th><th>Description</th></tr></thead><tbody><tr><td>Id</td><td>This field displays the Id of the job that acts as a unique identifier for the job.</td></tr><tr><td>Title</td><td>This field captures the name of the job.</td></tr><tr><td>Current Status</td><td>This field indicates the current status of the job, whether it is Active, De-Activated, or Completed.</td></tr><tr><td>Execution Dttm</td><td>This field captures the execution date and time of the job.</td></tr><tr><td>Execution Result</td><td>This field indicates whether the job execution was successful or encountered errors.</td></tr><tr><td>Next Execution Dttm</td><td>This field shows the date and time for the next execution of the job.</td></tr><tr><td>Message</td><td>This field records any message linked to the job execution.</td></tr><tr><td>Record Count</td><td>If an export file has been included in the job execution, this field records the number of records within the file.</td></tr><tr><td>Is Resolved?</td><td>If any error has been encountered during the job execution, this field shows if the error has been resolved or not.</td></tr><tr><td>Action</td><td>Click on the "Search" icon below this field to access all the execution details associated with that specific job ID.</td></tr></tbody></table>

### Managing Log Entries

Users can perform the following actions within the Job Execution History:

* **Filter logs:** Use the provided filters to narrow down logs by date, status, or job type.

#### Filters

<table><thead><tr><th width="227">Filter</th><th>Description</th></tr></thead><tbody><tr><td>Status</td><td>This dropdown option allows users to narrow down the displayed job execution history based on the status of the job. </td></tr><tr><td>Data Records Only</td><td>Enable this option to omit the export job execution activities.</td></tr><tr><td>Exclude Resolved Errors</td><td>Enable this option to omit the job executions that encountered errors but have since been resolved.</td></tr><tr><td>Errors Only</td><td>Enable this option to view only those job executions that encountered errors. It helps in quickly identifying problematic executions and focusing on troubleshooting and resolution tasks.</td></tr><tr><td>Message</td><td>This search field allows users to search for specific keywords or phrases within the job execution history messages.</td></tr></tbody></table>

* **Download logs:** Export logs for external analysis or recordkeeping. To download the logs, click on the "Export" icon and select the desired file format.

  <figure><img src="/files/kyKiCcIe60Y6MzEKbIJr" alt=""><figcaption></figcaption></figure>

### Job Execution History Options

The job execution history module provides multiple options to manage and control the job execution.

#### Job Execution History Options

<table><thead><tr><th width="162">Field</th><th>Description</th></tr></thead><tbody><tr><td>Re-Run</td><td>Allows users to initiate the execution of a job again, enabling tasks to be re-executed for various reasons such as error correction or data refresh.</td></tr><tr><td>Stop</td><td>Halts the execution of a job that is currently in progress, providing a means to terminate tasks that may be running unexpectedly or in error.</td></tr><tr><td>Resolve</td><td>Allows the users to mark a job execution as resolved, indicating that any associated issues or errors have been addressed and resolved satisfactorily.</td></tr><tr><td>Un-resolve</td><td>Allows users to revert the status of a job execution back to unresolved, typically used when issues resurface or require further attention after being previously marked as resolved.</td></tr></tbody></table>

{% hint style="info" %}
Remember to periodically review and manage the Job Execution History to ensure optimal system performance and to keep track of your data import and export operations.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.xorosoft.com/xoroerp-1/utilities/job-schedules/job-execution-history.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.