Trigger.dev v4.6.1

3 improvements, 1 bug fix, and 3 server changes.

Improvements

• Show schedule policy warnings during development and deployment; schedule limit errors now surface as clear messages instead of internal stack traces.
• New CLI commands: projects create/get/rename, runs list/get/replay/cancel, and env set.
• Warn when a deployment uses the deprecated Node.js 21 runtime: deployment logs now include upgrade guidance, and the account associated with the deployment receives an email notification.

Bug fixes

• Fix the MCP server failing every tools/list call with "Date cannot be represented in JSON Schema".

Server changes

These changes are included in the v4.6.1 Docker image and are already live on Trigger.dev Cloud:

• The dashboard assistant now responds with investigation cards for run questions, carrying the run's timeline and links to the run, queue, or deployment. Charts and tables can be opened fullscreen or copied, including queue metrics. You can also ask about a different project or environment without switching to it first.
• Warn when Production projects still use Node.js 21, with a direct link to update instructions.
• Deployments now show the runtime their worker actually reported: Bun deployments are no longer labelled Node.js, and a deployment with no recorded runtime shows a dash instead of a guess.

How to upgrade

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

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