A nightly cleanup and a reminder chosen by a customer run on different clocks. Vercel Schedules, listed in public beta on all plans in Vercel’s November 5 changelog, supports both. The beta can run in production, preview, or custom environments, so teams can exercise a scheduled job before it reaches production.
The target depends on how the job is created
A static schedule lives in project configuration and takes effect on deployment. It runs on a recurring cadence and can call an HTTP path, invoke a private Vercel Function, or publish to a Vercel Queues topic. A cleanup that belongs to the application can be defined this way, with its own time zone.
A dynamic schedule takes effect without a deployment. The application can create it through the SDK, or a developer can use the CLI. Dynamic schedules target a queue topic and support both recurring and one-time runs. For a customer reminder, the application schedules delivery and a queue consumer does the work when the message arrives.
The dashboard shows run history and lets teams run an individual schedule on demand. Vercel also documents a timing window for delivery, a detail to check if a task has a tight deadline.
