Trigger.dev home page

Community
triggerdotdev/trigger.dev
triggerdotdev/trigger.dev

Introduction

Getting Started

Quick start
Upgrading from v2
Changelog
Feature matrix
Known issues
Limits & Performance

Fundamentals

/trigger folders
Tasks
Triggering
API keys
Task types
trigger.config file

Development

CLI dev command
Run tests

Deployment

Environment Variables
CLI deploy command
GitHub Actions
Deployment integrations

Writing tasks

Introduction
Logging and tracing
Errors & Retrying
Wait
Concurrency & Queues
Versioning
Machines
Idempotency
Reattempting & Replaying
Trigger filters
Notifications
Rollbacks
Using APIs
Middleware
Automated tests

Dashboard

Overview
Runs
Tests
Environment Variables

API reference

Functions
Objects
CLI
Runs API
Schedules API

Architecture

How it works
Multi-tenant queue
Reliability

Open source

GitHub repo
Self-hosting
Contributing

Help

FAQs
Community
Email us
Slack
Uptime status

Architecture

Architecture: How it works

An overview of how Trigger.dev v3 works under the hood.

This documentation is coming soon.

Assistant

Responses are generated using AI and may contain mistakes.

Was this page helpful?

Suggest edits Raise issue

Activate Schedule Multi-tenant queue

twitter github linkedin

Powered by Mintlify