> 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/sales-materials/logicnets-cron-job-module-ln-cjm.md). # LogicNets Cron Job Module (LN-CJM) ### License: Per LogicNets Installation Notes: 1. Available through Enterprise License options 2. Optionally licensed on a per web services transaction basis ### LN-CJM Description The LogicNets Cron Job Module allows designer users to create applications that schedule and monitor cron jobs--repetitive tasks scheduled to run automatically at a specified time and date and at a configurable time interval. The system can run these cron jobs in the background independent of on-demand or ongoing functionality of LogicNets applications. The CJM can be used to enable traditional batch processing where regular processes are performed at particular times on a pre-determined schedule. Designer users create logicnets that contain the actions that make up the cron job, and then they use the included Scheduler Monitor to schedule one or multiple cron jobs. With the Schedule Monitor they can set the date and time the cron job runs and review the status of each cron job that has run. ### Services and Deployment Considerations LogicNets offers training services (LN-TS) to assist designer users in creating and deploying their LogicNets cron jobs. LogicNets offers Design and Deployment services (LN-DS) to implement cron jobs and cron job management within LogicNets applications. These services usually require development and acceptance by customer of a formal SoW PG-AD3-260217 --- # 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/sales-materials/logicnets-cron-job-module-ln-cjm.md?ask=&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.