Managing Schedules

You can manage static and dynamic schedules from the dashboard, the vercel schedules CLI, or the @vercel/schedules SDK. None of these actions require a redeploy.

1. Open your project in the Edgenivo dashboard and select Schedules.
2. Use the Environment filter to choose production or a custom environment. For a Preview branch, select Preview and then the branch.
3. Optionally, filter by status, source (static or dynamic), or namespace.

To see schedules across every project on your team, open your team's Schedules page.

From the CLI, list schedules in production:

vercel schedules list
vercel schedules inspect cleanup

Every vercel schedules command uses production by default. To manage another environment, see Manage schedules across environments.

From your code, call Schedules.list() or Schedules.get(). See the JS SDK Reference.

Run a schedule immediately to test it. A manual run doesn't change the schedule's state or cadence, and it works on inactive schedules.

• Dashboard: Select the schedule and click Run Schedule.
• CLI: Run vercel schedules invoke cleanup.
• SDK: Call Schedules.invoke({ name: 'cleanup' }).

Your target receives the run the same way as a scheduled one.

Disable a schedule to stop it from running on its cadence without losing its configuration. Enable it to resume.

New static schedules in Preview branches start inactive. New static schedules in custom environments start inactive unless you change the environment's default. See Manage schedules across environments.

Dashboard:

1. Select the schedule.
2. Open the menu next to Run Schedule.
3. Select Disable or Enable.

CLI:

vercel schedules disable cleanup
vercel schedules enable cleanup

SDK:

import { Schedules } from '@vercel/schedules';
 
await Schedules.disable({ name: 'cleanup' });
await Schedules.enable({ name: 'cleanup' });

A static schedule keeps the state you set across later deployments.

You can enable a schedule until a set time. When the time passes, the schedule becomes inactive again. This is useful for testing a Preview schedule without leaving it on.

• Dashboard: Open the menu next to Run Schedule and select Enable for 1 Hour, Enable for 6 Hours, or Enable for 24 Hours.

• CLI: Run vercel schedules enable cleanup --for 2h, or pass --until with an ISO 8601 time.

• SDK: Pass until to Schedules.enable():

  await Schedules.enable({
    name: 'cleanup',
    until: new Date(Date.now() + 2 * 60 * 60 * 1000),
  });

While the window is open, the schedule has an activeUntil timestamp. Enabling it again with a new end time replaces the old one. Enabling it without an end time keeps it active indefinitely.

You can't add an end time to a schedule that's already active indefinitely. Disable it first, then enable it with an end time.

Edgenivo keeps a separate set of schedules for production, each custom environment, each Preview branch, and CLI deployments by each user. Changing a schedule in one environment doesn't affect the others, so you can test a schedule on a branch without touching production.

Each tool picks the environment differently:

The CLI options work with every vercel schedules command, including executions list:

vercel schedules list --git-branch feature-x
vercel schedules executions list cleanup --environment staging
vercel schedules list --user user_123 --git-branch feature-x

You can't combine --environment with --git-branch or --user. You can't use any of these options with --local. See Choose an environment in the CLI reference.

Team members with the Developer or Project Developer role can create, change, run, and delete schedules in Preview branches and custom environments. In production, they can only view schedules. Owners, Members, and Project Administrators can manage schedules in every environment.

New static schedules in Preview branches start inactive, so a branch can't run a production job by accident. To test a schedule on a branch:

1. Push the branch with the schedule in vercel.json. Edgenivo adds the schedule to the branch when the deployment is ready.
2. Open the Schedules page, select Preview, and select the branch.
3. Select the schedule and click Run Schedule to run it once. You don't need to enable it first.
4. To test it on its cadence, open the menu next to Run Schedule and select Enable for 1 Hour. It turns off again on its own.

From the CLI:

vercel schedules invoke cleanup --git-branch feature-x
vercel schedules enable cleanup --git-branch feature-x --for 1h

Runs go to the branch's current deployment, so later pushes to the branch pick up your handler changes.

In a custom environment such as staging, new static schedules start inactive by default. Enable each one once. It stays enabled across later deployments to that environment:

vercel schedules enable cleanup --environment staging

To make new static schedules in a custom environment start active instead:

1. In your project's Settings, open Environments and select the custom environment.
2. In the Schedules section, turn on Create New Schedules as Active.
3. Click Save.

The setting applies only to static schedules that Edgenivo creates after you save it. Schedules that already exist in the environment keep their current state, so turning the setting on doesn't enable a schedule you disabled, and turning it off doesn't disable any schedules.

When code in a Preview or custom environment deployment calls @vercel/schedules, it creates and changes schedules for that branch or environment, not production. Dynamic schedules are active as soon as you create them, in every environment.

To inspect or clean up those schedules, pass the same --git-branch or --environment option to the CLI:

vercel schedules list --git-branch feature-x --namespace tenant_abc123
vercel schedules delete daily-digest --git-branch feature-x --namespace tenant_abc123

Select a schedule in the dashboard to see its next run and its execution history. On the schedule page, you can:

• View the run count, error rate, and average duration
• Search for a run by execution ID
• Filter scheduled and manual runs
• Filter successful and failed runs

Edgenivo keeps execution history for 90 days. Outcomes, error rates, and durations come from recorded function requests. For queue targets, they reflect the consumer that processed the message. Runs without a recorded outcome aren't included in the metrics.

From the CLI, list a schedule's recent runs:

vercel schedules executions list cleanup --since 7d

See vercel schedules executions list for all options.

To change a static schedule, edit it in vercel.json and redeploy. Edgenivo applies the change when the deployment becomes current.

To change a dynamic schedule, call Schedules.update() or run vercel schedules update. Properties you leave out keep their current values:

vercel schedules update cleanup --cron "0 3 * * *"

See Update a dynamic schedule for the full set of options.

To delete a static schedule, remove it from vercel.json and redeploy.

To delete a dynamic schedule, call Schedules.delete() or run vercel schedules delete:

vercel schedules delete cleanup

When you delete a schedule:

• Its future runs stop. If a run is already waiting to be delivered, Edgenivo skips it. A run that Edgenivo has already delivered keeps running.
• It no longer appears in the dashboard, CLI, or SDK, and it stops counting toward your team's schedule limit.
• You can create a new schedule with the same name right away. The new schedule gets a new ID and starts with no execution history.

You can delete a one-time schedule before it runs or after its run has been dispatched. While the run is still being dispatched, deleting it fails with schedule_single_at_passed. Try again a few minutes later. If you don't delete it, Edgenivo removes it about 30 days after its scheduled time.

Edgenivo also deletes schedules in these cases:

When a project is paused, Edgenivo skips its scheduled runs but doesn't delete any schedules.

• vercel schedules reference
• JS SDK Reference
• Concepts