Trigger.dev v4.6.4

Fixes five-minute warm-start delays for projects using Zod 3.

If you deployed with Trigger.dev 4.6.0 through 4.6.3, use npm, and have Zod 3 pinned in package.json, a Zod import bug may have caused warm starts to fail and delayed your runs by approximately five minutes.

Cold starts were unaffected. Affected runs were automatically requeued. No data has been lost.

This is fixed in 4.6.4. Redeploy your tasks with the latest CLI:


npx trigger.dev@latest deploy

If you pin the CLI version, update it to 4.6.4 or later before redeploying. Existing deployments need a redeploy to receive the fix.

How to upgrade

Update the trigger.dev/* packages to v4.6.4 using your package manager:


npx trigger.dev@latest update # npm
pnpm dlx trigger.dev@latest update # pnpm
yarn dlx trigger.dev@latest update # yarn
bunx trigger.dev@latest update # bun

Self-hosted users: update your Docker image to ghcr.io/triggerdotdev/trigger.dev:v4.6.4.

Deploy your first agent today

Get set up in minutes, either on your own or with your coding agent.

Get started for free