> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/cron-job-scheduler/add-a-new-cron-job.md).

# Add a New Cron Job

1. To configure the Scheduler Monitor click on the *Config* tab on the left side of the screen.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-3d276eec69741fa9683e504564a073d4c11dd8dc%2Fcbeff41a-dae9-4836-9778-16f4d68695fe.png?alt=media)

   The system will open the configuration page for the Scheduler Monitor.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-cdf5033951ea20745e47a156e21613d520dcfaa7%2F1b865062-0d55-4af1-a863-18d016115630.png?alt=media)

   You select the cron job logicnets and configure the schedule on which the system runs the actions in the *Add new job configurations* section.
2. From the *Package* dropdown menu, select the name of the package in which your cron is located. Note: A cron has to be part of a published package for it to be listed in the *Package* dropdown menu.
3. Once you have selected a package the system will display in the *Folder* field a list of those folders available in the cronjobs subfolder of the published package you selected. Using the dropdown menu, select the name of the folder or location of the cron job logicnet.
4. With your package and folder selected the system will display the names of the logicnets from which you can select. Use the dropdown options in the *Job* field to select the name of the cron job.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-022c58dc9b10887577d6a99aff9b2e3fc4b60c88%2F727c49e4-b01c-4405-b39c-e055e9a78743.png?alt=media)
5. Once you have selected the cron job you can set the start time and intervals at which the system will run it. Enter the hour and minutes of the start time in the *Start @* field and select if that is AM or PM.
6. In the *Interval* field enter the number of seconds between when the system runs the cron. For example, if you put 3600 the system will run the cron once every 60 minutes, or once per hour (3600 seconds divided by 60).
7. Once you have finished entering your first cron click the *Add* button to add your cron to the list of configured cron jobs in the *Existing configured jobs* section.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-987e5a72638ebf4e8a43307acd0dc806274fe2af%2F48d55a31-343e-4686-a99a-2e7aa845250d.png?alt=media)

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-221d525734e3e7bc300c6fd131f4ebaa7827b1ab%2Fb24fb464-badd-49c7-b789-3dadd73ef04a.png?alt=media)
8. Then click the *Save Changes* button to save your changes.
9. Repeat the steps above until you have added and configured each of the crons you want in the Scheduler Monitor.


---

# 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://community-test.logicnets.com/release-9/platform-documentation/cron-job-scheduler/add-a-new-cron-job.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.