--- title: vercel schedules product: vercel url: /docs/cli/schedules canonical_url: "https://vercel.com/docs/cli/schedules" last_updated: 2026-09-22 type: reference prerequisites: - /docs/cli related: - /docs/schedules - /docs/schedules/concepts - /docs/schedules/local-development - /docs/schedules/configuration - /docs/schedules/manage summary: Inspect and manage schedules in production, a custom environment, a Preview branch, CLI deployments by a user, or a local development session with... install_vercel_plugin: npx plugins add vercel/vercel-plugin --- # vercel schedules > **💡 Note:** The `vercel schedules` command is currently in beta. Subcommands and options > may change before general availability. The `vercel schedules` command manages [Vercel Schedules](/docs/schedules) for your linked project. Use it to inspect, enable, disable, and run any schedule, and to create, update, and delete dynamic schedules that target a queue topic. > **💡 Note:** Commands manage production schedules by default. To choose another > environment, pass `--environment`, `--git-branch`, or `--user`. See [Choose > an environment](#choose-an-environment). ## Usage ```bash filename="terminal" vercel schedules [subcommand] ``` *Use a subcommand to manage schedules for the current project.* ## Commands | Command | Alias | Description | | --- | --- | --- | | `list` | `ls` | List schedules in a namespace | | `inspect ` | | Show a schedule | | `create ` | | Create a dynamic schedule | | `update ` | | Update a dynamic schedule | | `executions list ` | `executions ls ` | List execution history for a schedule | | `enable ` | | Enable a schedule | | `disable ` | | Disable a schedule | | `invoke ` | | Invoke a schedule immediately | | `delete ` | `rm`, `del` | Delete a schedule | You can list, inspect, enable, disable, and invoke static or dynamic schedules. You can only update and delete dynamic schedules. To change or remove a static schedule, edit your project configuration and redeploy. `get` remains a supported alias for `inspect`, but prints a deprecation warning. Use `inspect` for new commands. Subcommands support these shared options: | Option | Description | | --- | --- | | `--namespace ` | Schedule namespace. Defaults to `default`. | | `-e, --environment ` | Use production or a custom environment by name or ID. Defaults to production. | | `--git-branch ` | Use the schedules of a Preview branch. | | `--user ` | Use the schedules of CLI deployments by a Vercel user ID. Combine with `--git-branch` for CLI deployments associated with a branch. | | `--json` | Output as JSON. | | `--local` | Use the running `vercel dev` session. See [Manage schedules locally](#manage-schedules-locally) for supported commands. | ## Choose an environment Vercel keeps [separate schedules](/docs/schedules/concepts#environments) for production, each custom environment, each Preview branch, and CLI deployments by each user. Commands use production unless you choose otherwise: ```bash filename="terminal" vercel schedules list --environment staging vercel schedules enable cleanup --git-branch feature-x --for 2h vercel schedules executions list cleanup --git-branch feature-x vercel schedules list --user user_123 vercel schedules list --user user_123 --git-branch feature-x ``` *Manage schedules in the \`staging\` custom environment, on the \`feature-x\` Preview branch, and for CLI deployments by \`user\_123\`.* - `--environment` accepts `production` or the name or ID of a custom environment. The CLI omits the environment selector when you pass `production`. - `--git-branch` by itself accepts a branch in your project's linked Git repository. - `--user` accepts a Vercel user ID and selects that user's CLI deployments. Combine it with `--git-branch` when those deployments include Git branch metadata. - You can't combine `--environment` with `--git-branch` or `--user`. You can't use any of these options with `--local`. Every subcommand accepts these options, including `create`, `update`, and `delete` for dynamic schedules. When a command prints a follow-up command, such as the command for the next page of results, it keeps the same non-production environment option. ## Manage schedules locally Start [`vercel dev`](/docs/schedules/local-development), then pass `--local` to a management subcommand. This option targets the running Schedules session for the current project directory. Local commands require no cloud login or project link. Use `--cwd` to select another project directory. The command rejects stale or ambiguous sessions and never falls back to cloud requests. You can't combine `--local` with `--scope`, `--team`, or `--token`. ```bash filename="terminal" vercel schedules list --local vercel schedules inspect daily-cleanup --local ``` *Manage schedules in the running local development session.* `executions list` rejects `--local`. Read the `vercel dev` output for local executions. ## Create a schedule Create a recurring schedule with `--cron` or a one-time schedule with `--at`. You must also provide a queue topic: ```bash filename="terminal" vercel schedules create daily-cleanup --cron "0 2 * * *" --topic scheduled-cleanup vercel schedules create send-reminder --at 2026-09-17T10:00 --timezone America/New_York --topic reminders ``` *Create recurring and one-time schedules in the default namespace.* The `create` subcommand supports these options: | Option | Description | | --- | --- | | `--cron ` | Cron expression for a recurring schedule. Can't be combined with `--at`. | | `--at ` | Local date and time in `YYYY-MM-DDTHH:mm` or `YYYY-MM-DDTHH:mm:00` format. Omitted seconds are stored as `:00`. Can't be combined with `--cron`. | | `--timezone ` | IANA timezone used to evaluate the expression. Defaults to UTC. | | `--jitter ` | Jitter window from 1 through 15 minutes. | | `--topic ` | Required queue topic to target. | | `--payload ` | JSON payload, up to 8 KB, included in each queue message. | The shortest interval between cron firings must be at least as long as the jitter window. On Hobby, omit `--jitter` or set it to `15`. Other values are rejected, and cron schedules can run at most once every 15 minutes. For the one-time `--at` format, see [One-time expressions](/docs/schedules/configuration#one-time-expressions). ## List and inspect schedules List schedules in the default namespace, continue from a cursor, or inspect one schedule: ```bash filename="terminal" vercel schedules list vercel schedules list --namespace jobs --limit 50 vercel schedules list --next vercel schedules inspect daily-cleanup --json ``` The `list` subcommand supports `--limit ` from 1 through 100, which defaults to 20, and `--next ` for pagination. ## List execution history List recent executions for a static or dynamic schedule: ```bash filename="terminal" vercel schedules executions list daily-cleanup vercel schedules executions list daily-cleanup --execution schx_abc123 vercel schedules executions list daily-cleanup --since 7d --until 1d --json ``` By default, the command lists the last 24 hours in descending order. Select a range of up to 30 days with these options. | Option | Description | | --- | --- | | `-s, --since