# Vercel — Introducing Vercel Schedules

- Company: Vercel (vercel.com)
- Announced: 2026-11-04T13:00:00+00:00
- Category: developer-tool-release
- Coverage: not counted
- Announcement: yes
- Group: announcements
- Source: https://vercel.com/blog/introducing-vercel-schedules
- Record: https://forck.live/items/32300-introducing-vercel-schedules
- Subject: v0 / AI SDK / AI Gateway

Vercel is introducing Vercel Schedules, a way for agents and applications to create, change or cancel one-time and recurring schedules through code without redeploying. Cron jobs are defined once in code and updated by editing config and redeploying, which Vercel says no longer fits agents that interact with users as work evolves. Schedules builds on the static approach used by Vercel Cron Jobs but lets users and agents decide when work should happen while the application is still running. Static schedules keep timing in vercel.json or Build Output API configuration and sync on deploy, while dynamic schedules are managed at runtime through the JS SDK, CLI or API and support one-time and recurring work through Queue topics. When a task is due, Vercel uses Queues to deliver the saved request to the app, which supplies the code to check permissions and start the agent. Vercel Schedules is now in Public Beta, and scheduled work can be tested on Preview deployments and in custom environments before Production.

## Evidence

Verbatim from https://vercel.com/blog/introducing-vercel-schedules:

> Cron jobs are useful for work that needs to happen regularly. You can use them to do things such as back up your database on a schedule, or keep data in sync between two systems.
> 
> You define them once in code and then can update them by editing their config and redeploying. But today, agents interact with users as work evolves, and schedules need to be updated in real time.
> 
> We built Vercel Schedules to allow agents and applications to create, change, or cancel one-time and recurring schedules through code, without redeploying.
> 
> Copy link to heading What are Vercel Schedules?
> 
> Schedules builds on the static approach used by Vercel Cron Jobs , but are designed to let users and agents decide when work should happen while your application is still running. A schedule tells Vercel when to trigger a task and where to send it. Your application provides the code that carries out the work.
> 
> You can use schedules for both static and dynamic jobs:
> 
> Static schedules keep the timing in vercel.json or Build Output API configuration and sync when you deploy. You can use them to call private functions or HTTP paths, or send messages to Queue topics .

---

Record: https://forck.live/items/32300-introducing-vercel-schedules
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md