> For the complete documentation index, see [llms.txt](https://docs.lingoql.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lingoql.com/sub0/apis-abi/cron-jobs.md).

# Cron Jobs

Cron jobs let Sub0 run an actionable on a schedule.

They do not need a client request once deployed.

### Basic example

```json
{
  "id": "cleanup-job-01",
  "resource": "cleanup-job",
  "actionables": [
    {
      "id": 1,
      "mode": "QUERY",
      "run_in_background": true,
      "sql_query": {
        "query": "DELETE FROM sessions WHERE expires_at < $1",
        "parameters": ["$DATETIME"]
      },
      "cron_job": {
        "execution_interval": "0 0 0 * * *"
      }
    }
  ]
}
```

This runs every day at midnight.

### Cron format

Sub0 uses a six-part cron expression:

```
second minute hour day-of-month month day-of-week
```

Example:

```
0 0 0 * * *
```

### Good use cases

* scheduled cleanup
* recurring reports
* billing and renewal workflows
* periodic syncs

### Keep it safe

* Put `cron_job` on the actionable that should run
* Use one scheduled actionable per resource when possible
* Keep `run_in_background: true` on scheduled work

### Why it matters

Cron jobs let you automate backend work without adding another scheduler to your stack.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.lingoql.com/sub0/apis-abi/cron-jobs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.