Katia Bulatova
020dad22a0
The whole transcript lived in one JSONB array on `chats` and every turn rewrote it, so bytes written grew as N squared: a 40-message chat wrote ~3.2 MB plus comparable WAL for one appended message. Dedupe was a `jsonb_array_elements` scan, the quota count scanned every chat the user owns, and a wholesale snapshot write could delete a message another process had appended — patched until now by reading the row `FOR UPDATE` and merging in JS. `chat_messages` replaces it: primary key `(chat_id, message_id)`, so a redelivered message is a conflict rather than a duplicate, and `UNIQUE (chat_id, position)`, so a lost or duplicated position is impossible rather than unlikely. Positions come from `chats.next_message_position`, bumped by the same single statement that reads it. Concurrent writers therefore get disjoint contiguous ranges, and the row lock is released with the statement instead of being held across a JS merge — the lock was never the problem, reading and rewriting a large blob under it was. A batch reserves one contiguous range and keeps its incoming order; a message already stored keeps the position it was first given, which is why a wake appended mid-turn now sits before the turn's later messages rather than after them. `role` is lifted out of the payload so `countUserMessages` is a `count(*)` over an index instead of an array explosion. No counter column on `chats`: that would be one more thing to keep in sync across insert, backfill and controlled update, for no proven need. The writers now split by intent. A new message is an INSERT. A repeat of the same durable event — `appendChatMessageOnce`, the sweep's closing card — is ON CONFLICT DO NOTHING and writes nothing at all, not the row, not the position, not the chat's timestamps. A turn's batch is ON CONFLICT DO UPDATE guarded by `is distinct from`, so re-persisting an unchanged 40-message transcript writes zero rows; when a message does need finalising, only its body changes and its identity and position stand. There is no wholesale replacement of a chat left anywhere. `mergeStoredMessages` and `writeMergedMessages` are deleted rather than left beside the new API, so there is no ready-made way back to the bug. `appendChatMessage` goes with them: nothing outside its own test called it, and a non-deduped append has no meaning now that identity is the key. Migration 0019 is additive. It creates the table, backfills from `jsonb_array_elements … WITH ORDINALITY` using each message's own id (deriving a stable one from the chat and ordinal for a legacy message without one, and keeping the first of a duplicated id exactly as the old merge did), then advances each chat's allocator past what it wrote. `chats.messages` stays for the transition and nothing reads or writes it; dropping it is a separate later migration.
Build and deploy fully‑managed AI agents and workflows
Website | Docs | Issues | Example projects | Feature requests | Public roadmap | Self-hosting
About Trigger.dev
Trigger.dev is the open-source platform for building AI workflows in TypeScript. Long-running tasks with retries, queues, observability, and elastic scaling.
The platform designed for building AI agents
Build AI agents using all the frameworks, services and LLMs you're used to, deploy them to Trigger.dev and get durable, long-running tasks with retries, queues, observability, and elastic scaling out of the box.
-
Long-running without timeouts: Execute your tasks with absolutely no timeouts, unlike AWS Lambda, Vercel, and other serverless platforms.
-
Durability, retries & queues: Build rock solid agents and AI applications using our durable tasks, retries, queues and idempotency.
-
True runtime freedom: Customize your deployed tasks with system packages – run browsers, Python scripts, FFmpeg and more.
-
Human-in-the-loop: Programmatically pause your tasks until a human can approve, reject or give feedback.
-
Realtime apps & streaming: Move your background jobs to the foreground by subscribing to runs or streaming AI responses to your app.
-
Observability & monitoring: Each run has full tracing and logs. Configure error alerts to catch bugs fast.
Key features:
- JavaScript and TypeScript SDK - Build background tasks using familiar programming models
- Long-running tasks - Handle resource-heavy tasks without timeouts
- Durable cron schedules - Create and attach recurring schedules of up to a year
- Trigger.dev Realtime - Trigger, subscribe to, and get real-time updates for runs, with LLM streaming support
- Build extensions - Hook directly into the build system and customize the build process. Run Python scripts, FFmpeg, browsers, and more.
- React hooks - Interact with the Trigger.dev API on your frontend using our React hooks package
- Batch triggering - Use batchTrigger() to initiate multiple runs of a task with custom payloads and options
- Structured inputs / outputs - Define precise data schemas for your tasks with runtime payload validation
- Waits - Add waits to your tasks to pause execution for a specified duration
- Preview branches - Create isolated environments for testing and development. Integrates with Vercel and git workflows
- Waitpoints - Add human-in-the-loop judgment at critical decision points without disrupting workflow
- Concurrency & queues - Set concurrency rules to manage how multiple tasks execute
- Multiple environments - Support for DEV, PREVIEW, STAGING, and PROD environments
- No infrastructure to manage - Auto-scaling infrastructure that eliminates timeouts and server management
- Automatic retries - If your task encounters an uncaught error, we automatically attempt to run it again
- Checkpointing - Tasks are inherently durable, thanks to our checkpointing feature
- Versioning - Atomic versioning allows you to deploy new versions without affecting running tasks
- Machines - Configure the number of vCPUs and GBs of RAM you want the task to use
- Observability & monitoring - Monitor every aspect of your tasks' performance with comprehensive logging and visualization tools
- Logging & tracing - Comprehensive logging and tracing for all your tasks
- Tags - Attach up to ten tags to each run, allowing you to filter via the dashboard, realtime, and the SDK
- Run metadata - Attach metadata to runs which updates as the run progresses and is available to use in your frontend for live updates
- Bulk actions - Perform actions on multiple runs simultaneously, including replaying and cancelling
- Real-time alerts - Choose your preferred notification method for run failures and deployments
Write tasks in your codebase
Create tasks where they belong: in your codebase. Version control, localhost, test and review like you're already used to.
import { task } from "@trigger.dev/sdk";
//1. You need to export each task
export const helloWorld = task({
//2. Use a unique id for each task
id: "hello-world",
//3. The run function is the main function of the task
run: async (payload: { message: string }) => {
//4. You can write code that runs for a long time here, there are no timeouts
console.log(payload.message);
},
});
Deployment
Use our SDK to write tasks in your codebase. There's no infrastructure to manage, your tasks automatically scale and connect to our cloud. Or you can always self-host.
Environments
We support Development, Staging, Preview, and Production environments, allowing you to test your tasks before deploying them to production.
Full visibility of every job run
View every task in every run so you can tell exactly what happened. We provide a full trace view of every task run so you can see what happened at every step.
Getting started
The quickest way to get started is to create an account and project in our web app, and follow the instructions in the onboarding. Build and deploy your first task in minutes.
Useful links:
- Quick start - get up and running in minutes
- How it works - understand how Trigger.dev works under the hood
- Guides and examples - walk-through guides and code examples for popular frameworks and use cases
Self-hosting
If you prefer to self-host Trigger.dev, you can follow our self-hosting guides:
- Docker self-hosting guide - use Docker Compose to spin up a Trigger.dev instance
- Kubernetes self-hosting guide - use our official Helm chart to deploy Trigger.dev to your Kubernetes cluster
Support and community
We have a large active community in our official Discord server for support, including a dedicated channel for self-hosting.
Development
To setup and develop locally or contribute to the open source project, follow our development guide.