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

# Designate a Logicnet as a Cron Job

Before configuring the Cron Job Scheduler, you must first create logicnets that contain the actions the cron job will perform. You can create one or more logicnets, with each logicnet containing a schedulable cron job. These logicnets must be placed in a specific folder called "cronjobs" inside the logicnets folder.

Note: For the system to identify a cron job, it must meet the following conditions:

* it must be placed in the "cronjobs" subfolder
* it may not contain any spaces in the name, and
* it must be part of a published project (and follow the rules for published project names, 0-9, a-Z etc. and avoid '-')

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-ca11f6806614d9470bb890c6b44345ca468cdd11%2F5d46caad-361f-4e4e-abb2-361799239afe.png?alt=media)


---

# 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/designate-a-logicnet-as-a-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.