> 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/create-a-cron-job-logicnet.md).

# Create a Cron Job Logicnet

To create a cron job you model a logicnet and each cron job you create should be in its own logicnet.

1. Open the project in which you want to create your cron job.
2. Navigate to the logicnets folder in the tree view and create a subfolder called cronjobs.
3. In the cronjobs folder, create a logicnet for the cron job . Note: You can add multiple cron job logicnets to this folder. Each logicnet should be a separate, invokable cron job. Your cron jobs can reach out to logicnets outside of the cronjobs subfolder, but the cron job logicnets themselves must be in the cronjobs subfolder.
4. Model the cron job logicnet to perform the processing you want it to do. Remember to use only process nodes and system-facing node types. User-facing node types cannot be used in cron jobs.
5. Add any system messages (status, status code details) that you want to see/show in the Monitor (to confirm the cron job was successful, report number of transactions processed, etc.)
6. When you have finished creating your cron job publish the project.


---

# 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/create-a-cron-job-logicnet.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.