> For the complete documentation index, see [llms.txt](https://docs.appstrategy.com/apprules-r-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appstrategy.com/apprules-r-documentation/platform/platform-features/creating-and-running-projects/running-projects/project-scheduling.md).

# Using the Scheduler

Before scheduling a project check that your project dabase is effectively eligible to use scheduling Go to Admin Center --> Project Database Directory, Include in Scheduler must be checked.

<div data-with-frame="true"><figure><img src="https://1923141441-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MFjmFrZ8sef1J7qkr6H%2Fuploads%2FNiToSPElgBIzfFVwHAZI%2Fimage.png?alt=media&amp;token=4662b80b-baf6-4427-8ec8-e04a7842f1fb" alt=""><figcaption></figcaption></figure></div>

To schedule a job, display the job scheduling window as follows:

1 - Go to Workflows option from the Settings Menu and select your workflow or click the Workflow button on the currently displayed project.

2 - In the window displayed, click on the Schedule Tab:

<div data-with-frame="true"><figure><img src="https://1923141441-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MFjmFrZ8sef1J7qkr6H%2Fuploads%2F4vBp4DyJnj1LJamYJwfu%2Fimage.png?alt=media&amp;token=b31cbeec-bf64-421f-afc5-3ba4abf6d685" alt=""><figcaption></figcaption></figure></div>

**Select Scheduled State and enter the required fields:**

* Next Run Date/Time: initialize with the first launching date
* End Run Data/Time; Set the ending date for the scheduling (Run Until date)
* Frequency: Preset (will fill the cron settings for you) or Custom
* Hour:  7-22 to run between 7 and 22h59
* Day of Week= 0 to 6 (sunday to saturday)

**Cron examples:**

| min  | hour | day/month | month  | day/week | Execution time                                         |
| ---- | ---- | --------- | ------ | -------- | ------------------------------------------------------ |
| 30   | 0    | 1         | 1,6,12 | \*       | — 00:30 Hrs  on 1st of Jan, June & Dec.                |
| 0    | 20   | \*        | 10     | 1-5      | –8.00 PM every weekday (Mon-Fri) only in Oct.          |
| 0    | 0    | 1,10,15   | \*     | \*       | — midnight on 1st ,10th & 15th of month                |
| 5,10 | 0    | 10        | \*     | 1        | — At 12.05,12.10 every Monday & on 10th of every month |

The Scheduler Service must be installed and started on the machine. see: [Scheduler Service Setup](/apprules-r-documentation/platform/self-hosting/software-installation/scheduler.md) &#x20;


---

# 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.appstrategy.com/apprules-r-documentation/platform/platform-features/creating-and-running-projects/running-projects/project-scheduling.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.