> ## Documentation Index
> Fetch the complete documentation index at: https://docs.revolte.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Cron

> Configure repository preferences and environment settings for a scheduled background job.

This guide explains how to configure a **Cron** resource in Revolte. Cron jobs are modular building blocks used for recurring tasks and background processing.

## Combined deployments

If your application requires compute (API) alongside a scheduled task, you should select one of the following presets during the **Choose a Preset** step:

* **Webservice + Cron**
* **Webservice + Database + Cron**
* **Cron + Database**
* **Cron + Cache**
* **Cron + Database + Cache**

> **Note:** For all combined presets, the core configuration workflow is identical to a standard [Web Service](/guides/deployments/web-services). This guide focuses specifically on the supplemental **Cron** settings described below.

<Steps>
  <Step title="Choose a Preset">
    Select the **Cron** tile for a standalone instance, or choose one of the combined presets listed above for integrated deployments.
  </Step>

  <Step title="Cron — Environment Settings">
    <img src="https://mintcdn.com/poddle-54594c3d/q0Rk3K5lGk3vHIWm/image-v2/guides/web-service/cron.png?fit=max&auto=format&n=q0Rk3K5lGk3vHIWm&q=85&s=8f78175f1437be7a09ff33e984f37993" alt="Cron tab — QA environment" width="752" height="682" data-path="image-v2/guides/web-service/cron.png" />

    The **QA** environment tab is selected. You can define independent schedules and resource specifications for **Preview**, **QA**, **Staging**, and **Production**.

    The center panel shows the Cron form for the active environment:

    * **Service Name** — Enter a unique identifier for this cron job (e.g., `daily_cleanup`).
    * **Entry Point** — The script or command that starts the task (e.g., `scripts/cleanup.js`).
    * **Specifications**
      * **CPU & Memory** — Choose a compute tier appropriate for the job's complexity.
      * **Storage value** — Disk space in GB allocated for the job's temporary files.
    * **Properties**
      * **Scheduler** — Define the execution frequency using standard cron syntax (e.g., `cron(0 0 * * *)` for daily at midnight).
    * **Pre Script** — Commands to run before the main task (e.g., installing dependencies or setting up data).
  </Step>
</Steps>

> **Tip:** Test your cron expressions using a validator to ensure they trigger at the expected intervals before committing.

***

**Quick Reference:**

* [Technical Cron Overview](/deployments/services/cron-jobs)
* [Cron Resource Specifications](/yaml/environment-settings/resource-specifications/cron)