Trigger.dev v4.8.8

OIDC rate limit error handling, run suspend reliability, and an expanded remote MCP server with bulk actions, tag management, and stream reading.

3 improvements and 6 server changes.

Improvements

  • The MCP list_runs tool can now filter runs by queue, batch, schedule, and bulk action. Its descriptions clarify that period takes precedence over from and to. (25c9430e)
  • auth.getOIDCToken() now throws RateLimitError with code RATE_LIMIT_EXCEEDED when OIDC token requests remain throttled after retries, for both per-run and shared API limits. If you catch these errors with instanceof OIDCTokenError, update your handler to also check for RateLimitError. Other OIDC errors and retry behavior are unchanged. (04b139db)
  • Fixed a case where a run's suspend was lost if the supervisor's first handoff attempt failed unexpectedly. (9e5ddbec)

Server changes

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

  • The remote MCP server can now list run tags, search and read logs, add tags, update metadata, reset idempotency keys, reschedule delayed runs, and read a run's streamed output. Run details include metadata values. It can also list, read, create, and abort bulk actions that cancel or replay many runs at once: you approve every bulk action before it executes. Edits that would change nothing are refused without prompting.
  • The remote MCP server now has OAuth scopes for errors, queues, tasks, batches, waitpoints, environments, deployments, branches, environment variable names, and project settings. Existing connections keep the access they already have.
  • The dashboard now shows only the last four characters of root API keys. Existing keys still work, but can no longer be copied from the dashboard. Create a separate API key for each integration.
  • External OIDC token requests now count against the same environment rate limit as other API requests, with the per-run limit unchanged.
  • A run's Session link now opens the session at that run.
  • Reopening the time filter keeps an exact date range selected instead of switching back to "in the last".

How to upgrade

Update the trigger.dev/* packages to v4.8.8 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.8.8.

Deploy your first agent today

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

Get started for free