> For the complete documentation index, see [llms.txt](https://docs.biscit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.biscit.com/ekr-user-guide/how-to/how-to-schedule-maintenance-jobs-in-kinetic.md).

# How to Schedule Maintenance Jobs in Kinetic

This guide outlines the process for managing and scheduling service tasks within the Maintenance Job section of Kinetic.

{% hint style="warning" %}
This documentation contains instructions that are done in Epicor Kinetic and might be outdated. For more detailed and updated instructions, refer to the Epicor Kinetic Web Help.
{% endhint %}

1. In Kinetic at the **Maintenance Job** section, select a Maintenance Job from the list<br>

   <figure><img src="https://3143154457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFuMjREj8WHcxhf8dRWZN%2Fuploads%2FLobzT4Veecgu7WKO9Gu9%2Fimage.png?alt=media&amp;token=2d2638d8-c1b8-4a88-8e0e-903c6ecbfd40" alt=""><figcaption></figcaption></figure>

2. Take note of the **Required by** date of a **Maintenance Job**, this will be basis on scheduling the **Maintenance** **Job**.  \ <br>

   <figure><img src="https://3143154457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFuMjREj8WHcxhf8dRWZN%2Fuploads%2FYbyJJTI8DcbOOWQJ1iou%2Fimage.png?alt=media&amp;token=9bc820e9-93e7-423e-96eb-5fd9b8248080" alt=""><figcaption></figcaption></figure>

3. To Schedule a **Maintenance Job**, click on the three dots on the upper right side of the **Maintenance Job** screen and select **Job Scheduling**.<br>

   <figure><img src="https://3143154457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFuMjREj8WHcxhf8dRWZN%2Fuploads%2FeqzhodbpqmIEjbspDOY3%2Fimage.png?alt=media&amp;token=b38524eb-628e-4929-a90c-ca48a9aa0aa1" alt=""><figcaption></figcaption></figure>

4. Ensure that the **Due Date** is one day ahead of the **Required By** date and set it and click **OK**.\ <br>

   <figure><img src="https://3143154457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFuMjREj8WHcxhf8dRWZN%2Fuploads%2FZC3HtWPBpyPJGpWLAWzu%2Fimage.png?alt=media&amp;token=ac657889-775a-4829-a1eb-2582843573e3" alt=""><figcaption></figcaption></figure>

5. The **Maintenance Job** that was scheduled can be then be visible in the **Active Rentals** timeline found in the **EKR** Home Page as red bars.\ <br>

   <figure><img src="https://3143154457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFuMjREj8WHcxhf8dRWZN%2Fuploads%2FNBB0GUpu5vkqLjp54Owp%2Fimage.png?alt=media&amp;token=2c9096fb-46a0-4616-b872-de79812a0b04" alt=""><figcaption></figcaption></figure>

**Note**: Maintenance Jobs must be closed, otherwise they will keep rolling to the current date.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.biscit.com/ekr-user-guide/how-to/how-to-schedule-maintenance-jobs-in-kinetic.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
