# Cron jobs

> Run commands on a schedule, trigger them on demand, and review run history.

Source: https://gheima.ma/docs/cron-jobs

Cron jobs run a command on a schedule, isolated like your apps. Use them for backups, digests, cleanups, or any recurring task.

### Create a job

1. **New cron job** — On the Cron jobs page, click “New cron job” and name it.
2. **Set a schedule** — Pick a preset, such as "Hourly" or "Daily", or type a cron expression like 0 * * * *. A plain-language description shows when it runs. Schedules run in UTC.
3. **Set the command** — Enter the command to run, for example npm run task. Optionally run it against a service’s image and environment, or the base image.

```
0 * * * *
```

Runs at the start of every hour. Your plan sets the minimum interval allowed.

### Run now & history

- Click "Run now" to trigger a job immediately.
- Pause a job with its toggle, without deleting it.
- Run history lists recent runs with their status, duration, exit code, and logs.

### Schedule options & limits

- `Minimum interval`: Your plan sets the smallest allowed gap between runs.
- `Timezone`: UTC by default, and the dashboard creates every job in UTC. Set timezone through the API to evaluate the schedule in another zone.
- `Timeout`: A run that exceeds its timeout is stopped. The default is 300 seconds and the maximum is 3,600. Set timeoutSeconds through the API.
- `Target`: Run against a service’s image and environment, or the base image.

> Result: Your command runs on schedule, on demand when you need it, with a full history of past runs.

---

All docs: https://gheima.ma/docs.md