vercel implements scheduled jobs for JS/TS

Introduced 2026-05-09 · score 0.96

HOW TO USE IT

For a JavaScript or TypeScript project using a static scheduled job, define a `type: "job"` service with `trigger: "schedule"` in `vercel.json` and point it to a file that exports a default function. Deploy it with Vercel; dynamic schedules and local `vc dev` support were not included in this change.

{
  "services": {
    "cleanup": {
      "type": "job",
      "trigger": "schedule",
      "entrypoint": "jobs/cleanup.js",
      "schedule": "* * * * *"
    }
  }
}

WHY THIS HELPS

Configure scheduled jobs for a JavaScript or TypeScript project on Vercel.

REQUIREMENTS AND LIMITATIONS

Version: 53.3.0
services.<name>.type (required): Set to `"job"` for a scheduled job.
services.<name>.trigger (required): Set to `"schedule"` to trigger the job on a schedule.
services.<name>.entrypoint (required): Path to the job file; it must export a default function, invoked once per tick.
services.<name>.schedule (required): Static cron expression for the job schedule.
Prerequisite: Use Vercel CLI 53.3.0 or later for the feature introduced in this release.
Prerequisite: The entrypoint file must export a default function.
Prerequisite: Cron invocations can be secured by setting the project environment variable `CRON_SECRET`; Vercel sends it in the Authorization header. The change's dispatcher verifies it when set.
Docs conflict: The release commit says dynamic schedules and `vc dev` support are future work; they are not available for this feature in the change. https://github.com/vercel/vercel/commit/b4ada64

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card

Tools change faster than your agent’s training data.

Changes

vercel implements scheduled jobs for JS/TS