Trigger.dev September 2026 product update

Trigger.dev update – September 2026 Hey [First name], 👋 Here's what's new in Trigger.dev this month. Check out our full changelog for more details. Multiple concurrency limits per task Cap each tenant and the whole task at once with perKey: 1 and total: 10, or declare a named limit with concurrencyLimit() and share one pool across every task that calls the same rate-limited API. A run only starts when every limit it holds has room, and you can change any limit at runtime without a deploy. Learn more Concurrency metrics and queue health The Concurrency page now charts backlog, throttling, and scheduling delay (the gap between when a run could start and when it does) for every queue and concurrency key. Find the stuck queue and what's capping it, then pause it, override its limit, or archive queues you no longer use from the same page. Learn more Version skew protection: runs wait for their matching deploy Runs triggered while your tasks are still deploying now wait for the deployment built from the same commit, instead of falling back to the previous version. It replaces the atomic deployments setup: connect the Vercel integration and it’s on automatically; anywhere else, deploy with —external-id and send the same id from your app. Learn more Preview branches now archive themselves Set a policy once and any preview branch that hasn't had a deployment in that many days gets archived automatically (14 days by default). Put long-lived branches like main or staging on a keep list, and see exactly which branches the next cleanup will archive before you save. Learn more Customize the runs list with columns and smart columns Show, hide, and reorder the columns on any runs list, then add smart columns that pull a single value out of each run's payload, metadata, or output with a JSON path. Your layout lives in the URL, so a tuned view is a link you can bookmark or drop in a thread for a teammate. Learn more Themes & Accessibility Choose Light, Dark, Black, or White for the dashboard, or follow your system and pick which theme to use on each side. New accessibility controls add stronger colors, underlined links, and a contrast slider that works with any theme. Learn more Set up Trigger.dev with your AI agent New projects lead with a Copy AI agent prompt button that gives Claude Code, Cursor, or any coding agent what it needs to go from an empty codebase to a registered task. With the Trigger.dev MCP server, the agent can start the dev server, trigger a test run, and read its trace without leaving the conversation. Learn more From the blog Zod 4 got rid of a bunch of CPUs for us Upgrading from Zod 3 to 4.5 cut CPU demand on one of our main worker services by nearly a third, raised batch throughput by 14%, and dropped task trigger p99 by 18%. One worker service alone runs nearly 100 million parses a day, and we're now Zod's first Platinum Sponsor. Read more Upgrading a 56TB database that's growing at 250GB per day with (nearly) no downtime We had to upgrade a 56TB Aurora Postgres cluster without taking Trigger.dev down, so we moved new runs and the control plane to PlanetScale and left old runs behind. When Aurora finally rebooted, the only thing that noticed was requests for old runs, for about 90 seconds. Read more How can we make Trigger.dev better for you? I personally respond to every reply. 🙂 James You are receiving this email because you opted in to receive updates from Trigger.dev Trigger.dev, 1 Ashley Road Altrincham Cheshire WA14 2DT Unsubscribe