Trigger.dev v4.5.9

1 breaking change, 5 improvements, and 9 server changes.

Highlights

trigger report health

The new trigger report health command gives a plain-language verdict on three questions: is work flowing, are the runs that start succeeding, and is the telemetry fresh enough to trust either answer. When something looks wrong it names the most likely cause and a next action.

The verdict is computed server-side, so the CLI, the new get_report MCP tool, and GET /api/v1/reports/health all return the same output with the same sparklines. In MCP hosts that support prompts, report is also available as a slash command.

Breaking changes

• Setting a queue concurrency limit higher than your environment limit is now rejected with an error instead of being silently reduced to the environment limit. A queue can no longer appear to have more capacity than it can actually get. Limits already saved are unchanged. (#4131)

Improvements

• trigger mcp now always starts the MCP server. The interactive install wizard has moved behind trigger mcp --install. Previously the wizard opened whenever stdout was a terminal, so any MCP host that spawned the command over a pseudo-terminal waited on a server that never started and eventually timed out. (#4131)
• Prevent build debug logs from including environment variable values. (#4420)
• Send the running CLI version when checking for platform notifications so notices can be limited to compatible CLI releases. (#4407)
• Fixed incorrect docs on auth.createPublicToken and the trigger-token helpers: expirationTime as a number is a Unix timestamp in seconds, not milliseconds. (#4388)

Server changes

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

• A queue's concurrency limit can now be set as a percentage of your environment limit, from the dashboard or the API. Percentage limits track the environment limit, so raising or lowering it re-divides capacity without editing every queue. (#4131)
• New queue overview for each environment: see every queue's backlog, throughput, concurrency against its limit, when it was throttled, and how long runs waited before starting. Each queue also gets its own page with the same numbers broken down per concurrency key. (#4131)
• A queue's concurrency keys are now paged and searchable, so a queue with thousands of keys shows all of them instead of only the busiest 50. (#4131)
• The agent detail page now uses the same layout as other metrics pages: filters pinned at the top, activity charts in a row beneath them, tabs and table scrolling with the page, and agent config in a resizable panel on the right. (#4131)
• Self-hosted instances can now serve deployed runs' API traffic from a different origin than the public one, per organization, via the INTERNAL_API_ORIGIN environment variable and a feature flag. (#4366)
• Fixed a bug where accepting an old invitation could escalate the role of a member already in the organization. Invitations now leave existing members' roles untouched, people already in an organization are no longer sent invitations to it, and the invite form names which addresses it skipped instead of failing with an unhelpful error. (#4409)
• Removed an unused internal dashboard sync route that is no longer part of any product surface. (#4400)
• Fixed error reports being attributed to the wrong request when several requests were in flight at once. (#4372)
• Invalid queries sent to the query API are no longer treated as internal errors, and a query that does fail is now recorded with the query text that produced it. (#4372)

How to upgrade

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

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