---
title: "Scheduled jobs (Ample changelog, October 15, 2026)"
description: "`ample job create` runs a command in one of your services, or an HTTP request to it, on a cron schedule in any time zone or at a fixed interval, whether or not the app has traffic. Request jobs carry an `Ample-Job-Token` header that matches the app's `AMPLE_JOB_TOKEN`. `ample job run <name> --wait` "
canonical_url: "https://ample.computer/changelog/2026-10-15"
last_updated: "2026-10-15"
author: "Ample Computer"
---

# Scheduled jobs

Week ending October 15, 2026. CLI 0.1.34.

- **Jobs.** `ample job create` runs a command in one of your services, or an HTTP request to it, on a cron schedule in any time zone or at a fixed interval, whether or not the app has traffic. Request jobs carry an `Ample-Job-Token` header that matches the app's `AMPLE_JOB_TOKEN`.
- **Jobs.** `ample job run <name> --wait` runs a job now and exits 0 if it succeeded. A failed run says who has to act and how, like a failed deploy, and `ample job runs` keeps the history with each run's output.
- **Manifest.** `[jobs.<name>]` in ample.toml declares jobs; `ample up` creates or updates each one after its service deploys.
- **Background work.** Work no request waits on, such as a queue or a render, can run under `ample-awake -- <command>` inside the server so it is not treated as idle. `ample server keep-awake <server> --for 30m` does the same from outside, for a series of commands.
- **MCP.** Every `ample job` command and `ample server keep-awake` are MCP tools (`ample_job_create`, `ample_job_run`, ...).

[All changes](https://ample.computer/changelog)