Task setup, retries, queues, real-time observability, and the self-hosting gotchas the quickstart skips.
Most background job solutions feel like infrastructure problems wearing an API costume. You spend more time configuring Redis queues and worker pools than actually building the tasks you need to run.
Trigger.dev takes a different approach: background tasks are TypeScript functions that live in your codebase. You write them like normal code, deploy them with your app, and Trigger.dev handles the scheduling, retries, queuing, and observability. Here’s how to get your first task running and what to watch out for when you go to production.
What Trigger.dev Actually Is
Trigger.dev gives you long-running background tasks with:
Retries — automatic retry with configurable backoff on failure
Queues — control concurrency so tasks don’t overwhelm downstream services
Waits — pause a task mid-execution and resume later (hours, days, weeks)
Real-time observability — live logs and run traces in the dashboard
AI…