Blog

Today we're excited to launch our v4 beta, that includes Run Engine 2. There are significant performance improvements like warm starts, a totally revamped dashboard, human in the loop tokens, and more.

What we learned writing a Cursor Rules file for Trigger.dev tasks, and 10 tips for writing your own

Sam Wright, Head of Operations and Partnerships at Huntr, explains how they use Trigger.dev to build AI agents for content generation and internal tooling.

Ben Duggan, Staff Software Engineer at MagicSchool AI, shares how they use Trigger.dev and Vercel's AI SDK to extract insights from millions of student interactions.

Learn how to build AI agents with Trigger.dev, and how they can help you build more resilient systems.

Pontus Abrahamsson, CEO and co-founder of Midday, deep dives into how they use Trigger.dev to reliably sync bank transactions for their 11,500+ customers.

A recap of all the new features we announced during our first launch week.

Warm starts, multi-region workers, self-hosted workers, and new waitpoints.

A bunch of improvements to our batch processing system, including new limits and dashboard visibility.

Trigger.dev now supports triggering tasks from the frontend.

Install system packages, like FFmpeg and Puppeteer, and modify the build process.

Keep your users updated with real-time task progress. Now with LLM streaming support and increased limits.

Agree Ahmed, CEO of NUMI, shares his story of how they have re-architected their code to use Trigger.dev, and how it has changed the way they think about building complex distributed systems.

Marc Seitz, co-founder of Papermark, runs through how they have used Trigger.dev to build a real-time PDF conversion service, with thousands of conversions successfully processed per month.

Learn how to scrape the top 3 articles from Hacker News and email yourself a summary every weekday at 9AM.

Learn how to use Trigger.dev with Supabase to create event-driven workflows. We'll cover triggering tasks from Edge Functions, performing database operations, and building a video processing pipeline with AI transcription.

Trigger.dev v3 is now out of beta and at v3.0.0. This release includes a new CLI, a revamped build system, and more.

We encountered an issue with xmin horizon blocking Postgres vacuuming, causing system slowdowns. Learn about our troubleshooting process, the solution we implemented, and our steps to prevent similar incidents in the future.

Trigger.dev v2 will reach end-of-life on January 31st 2025. Here's what you need to know and how to migrate to v3.

Today, I'm excited to announce that Trigger.dev v3 is now open to everyone. No more waitlist!

We recently experienced some service degradation and downtime due to event loop lag in our Node.js service. Here's how we diagnosed and fixed the issue.

There was a major incident which caused runs to process extremely slowly and the dashboard to be unavailable. Here's what happened and what we've changed to prevent it from happening again.

Today you can get early access to v3. No timeouts, easy reliability and a new dashboard for finding and fixing bugs.

Write regular code and gvet durability with no timeouts. This means writing long-running tasks is far easier than before.

Trigger.dev, the open source background jobs framework, has today announced a $3M seed round.