> For the complete documentation index, see [llms.txt](https://docs.copia.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.copia.io/docs/devicelink/jobs/managing-jobs-and-history.md).
# Managing Jobs and History
## Job Management
The Job Management section allows you to perform a backup job "now", add new Jobs, or Edit existing jobs. To Edit a job, select the menu caret on the right side of the Backup Now button, to access the additional menu options.
The Job list provides details in this view, such as the Agent, and the schedule. In addition, it provides the last activity that was performed with the Job.
## Job Notifications
Job Notifications are generated on a scheduled or demand basis. They are provided at a Site level for users who have access to that site. Configuration of Job notifications are done in the [User Profile](/docs/git-based-source-control/administration/profile-and-settings.md) section, explained in the [Notifications ](/docs/devicelink/administration/notifications.md)topic.
## Job History
Click on the *Jobs* tab and navigate to the *Job History* section. The columns highlighted at the top can be sorted ascending or descending by clicking on them.
Select the caret mark on the left to expand the row and view the commit message. For more information on activating automated commit message generation for backups, please see our Copilot documentation.
There are 5 possible outcomes for a Job run -- each of which are shown as a chip in the *Result* column:
| Job Outcome | Description |
| ----------------- | ------------------------------------------- |
| ⚪ **Pending** | Waiting for the Agent to start the Job |
| ⚪ **In Progress** | Agent is currently performing the Job |
| 🟢 **Up to Date** | Job was completed with no differences found |
| 🟠 **Modified** | Job was completed with differences found |
| 🔴 **Failed** | Job failed due to an error |
| 🔴 **Timed Out** | Job took too long to be completed |
{% hint style="info" %}
A Job will usually time out when its supporting Agent encounters an issue. Typically, this will occur if multiple Jobs overlap, there is not a sufficiently long enough timeout value set, or your Agent experiences other connectivity issues.
{% endhint %}
For Jobs that are not pending or in process, you can see the differences by pressing the *View Details* button. This button will display the differences between the device and the commit that was used in determining the results.
{% hint style="warning" %}
In some cases, the View Options that you are using when you press *View Details* in a DeviceLink backup may be "hiding" that actual difference that triggered the update. When viewing details in a DeviceLink backup, we recommend starting with View Options configured to not hide or ignore any details, and then add as desired.
{% endhint %}
## Job Summaries
In addition to the Job history table, you can view Job summaries in graphical form by using the [Site graphs](/docs/devicelink/sitesandagents/sites/organization-dashboard.md), available via the Site tab of the Dashboard, as seen below.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://docs.copia.io/docs/devicelink/jobs/managing-jobs-and-history.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.