Vercel Schedules vs Cron Jobs: Migration Guide
Vercel released Schedules in November 2026 to succeed Cron Jobs, featuring IANA time zones and metered pricing starting at $5 per 1M runs.
Stock photo for illustration only, not from the actual event
- Vercel introduced Schedules in public beta on November 5, 2026, as the successor to Cron Jobs.
- The new feature supports IANA time zones, private functions, and runtime queue integrations.
- Migrating requires updating method defaults from legacy GET to POST paths.
- Pro and Enterprise tiers incur metered pricing of $5 per 1M runs and $10 per 1M creations.
Vercel introduced Vercel Schedules on November 4, 2026, rolling out a public beta by November 5, 2026. Designed as the successor to traditional Cron Jobs, existing cron setups continue to run seamlessly without any forced cutover, allowing developers to migrate at their own pace.
While legacy Cron Jobs relied on static path-and-cron configurations in UTC, Schedules allows static configurations inside vercel.json or the Build Output API, alongside dynamic runtime management via SDK, CLI, or API. Additionally, preview environments default new static schedules to inactive, preventing branch deployments from accidentally triggering production workloads.
Static schedules support three distinct targets: private functions, HTTP paths, and queue topics. Private functions leverage experimentalTriggers without exposing public URLs, ensuring that only the scheduler can invoke them. Meanwhile, HTTP path targets remain public unless developers implement explicit authentication.
Stock photo for illustration only, not from the actual event
The shift from Cron Jobs to Schedules reflects Vercel's adaptation to modern asynchronous cloud architectures, particularly for AI agent workflows that require reliable background task management. Features like IANA time zone support and native queue integration offer much greater flexibility than basic URL pings.
A critical pitfall during migration is that path schedules default to POST requests, whereas legacy cron hits utilized GET. Developers must explicitly set requestMethod to GET when porting older handlers. Furthermore, running both crons and schedules for the exact same task simultaneously must be strictly avoided to prevent double-firing.
According to Vercel's November 6, 2026 documentation, Pro and Enterprise tiers charge $5 per 1 million execution runs and $10 per 1 million schedule creations beyond included allowances. Hobby tiers include fixed monthly allowances with a 15-minute jitter window, whereas paid tiers default to a 1-minute interval that is tunable between 1 and 15 minutes.
Source: Dev.to
Found something wrong in this article? Report an issue with this article
Comments
Leave a Comment