/* Tooltip style on the code block */
div[class="absolute top-11 left-1/2 transform -translate-x-1/2 -translate-y-1/2 hidden group-hover:block text-white rounded-lg px-1.5 py-0.5 text-xs bg-primary-dark"] {
  color:#1A1B1F;
  border-radius: 0.25rem;
}

/* Link anchor active state - icon container */
div[class="mr-4 rounded-md p-1"] {
  border-radius: 0.25rem;
  border: 1px solid #464748;
}

/* Link anchor default state - icon container */
div[class="mr-4 rounded-md p-1 zinc-box group-hover:brightness-100 group-hover:ring-0 ring-1 ring-gray-950/5 dark:ring-gray-700/40"] {
  border-radius: 0.25rem;
  border: 1px solid transparent;
}

Guides

Trigger.dev

v2 docs

Discord

List all schedules. You can also paginate the results.

List Schedules

The deduplication key used to prevent creating duplicate schedules

The external ID of the schedule. Can be anything that is useful to you (e.g., user ID, org ID, etc.)

The description of the generator in plain english

The cron expression used to generate the schedule

The unique ID of the schedule, prefixed with 'sched_'

The id of the scheduled task that will be triggered by this schedule

Defaults to UTC. In IANA format, if set then it will trigger at the CRON frequency in that timezone and respect daylight savings time.

The type of schedule, `DECLARATIVE` or `IMPERATIVE`. Declarative schedules are declared in your code by setting the `cron` property on a `schedules.task`. Imperative schedules are created in the dashboard or by using the imperative SDK functions like `schedules.create()`.

secretKey

List all schedules

Welcome to the Trigger.dev v3 documentation.

Introduction

How to get started in 3 minutes using the CLI and SDK.

Quick start

There are some hard and soft limits in v3 that you might hit.

Limits

Changelog

Roadmap

Your tasks live inside /trigger folders. Code in these is bundled and deployed together.

/trigger folders

Tasks are functions that can run for a long time and provide strong resilience to failure.

Tasks

Tasks: Overview

Tasks need to be triggered in order to run.

Triggering

How to authenticate with Trigger.dev so you can trigger tasks.

API keys

The simplest type of task which can be triggered from elsewhere in your code.

Regular tasks

A task that is triggered on a recurring schedule using cron syntax.

Scheduled tasks (cron)

This file is used to configure your project and how it's bundled.

trigger.config file

The trigger.config.ts file

The `trigger.dev dev` command is used to run your tasks locally.

CLI dev command

You can use the dashboard to run a test of your tasks.

Run tests

Any environment variables used in your tasks need to be added so the deployed code will run successfully.

Environment Variables

The `trigger.dev deploy` command can be used to manually deploy.

CLI deploy command

You can easily deploy your tasks with GitHub actions.

GitHub Actions

When you deploy to Vercel, automatically deploy your associated tasks.

Vercel integration

Tasks are the core of Trigger.dev. They are long-running processes that are triggered by events.

Writing tasks: Introduction

How to use the built-in logging and tracing system.

Logging and tracing

How to deal with errors and write reliable tasks.

Errors & Retrying

During your run you can wait for a period of time or for something to happen.

Overview

Wait: Overview

Wait for a period of time, then continue execution.

Wait for

Wait until a date, then continue execution.

Wait until

Wait until an event has been received, then continue execution.

Wait for event

Wait until a `Request` has been received at the provided URL, then continue execution.

Wait for request

Configure what you want to happen when there is more than one run at a time.

Concurrency & Queues

We use atomic versioning to ensure that started tasks are not affected by changes to the task code.

Versioning

Configure the number of vCPUs and GBs of RAM you want the task to use.

Machines

An API call or operation is “idempotent” if it has the same result when called more than once.

Idempotency

A replay is a copy of a run with the same payload but against the latest version in that environment. This is useful if something went wrong and you want to try again with the latest version of your code.

Replaying

Tags allow you to easily filter runs in the dashboard and when using the SDK.

Notifications

Get compute duration and cost from inside a run, or for a specific block of code.

Usage

Overview & Authentication

Trigger

Batch trigger a task with up to 100 payloads.

Batch trigger

List runs in a specific environment. You can filter the runs by status, created at, task identifier, version, and more.

List runs

Retrieve information about a run, including its status, payload, output, and attempts. If you authenticate with a Public API key, we will omit the payload and output fields for security reasons.


Retrieve run

Creates a new run with the same payload and options as the original run.

Replay run

Cancels an in-progress run. If the run is already completed, this will have no effect.

Cancel run

Updates a delayed run with a new delay. Only valid when the run is in the DELAYED state.

Reschedule run

Create a new `IMPERATIVE` schedule based on the specified options.

Create Schedule

Retrieve Schedule

Update a schedule by its ID. This will only work on `IMPERATIVE` schedules that were created in the dashboard or using the imperative SDK functions like `schedules.create()`.

Update Schedule

Delete a schedule by its ID. This will only work on `IMPERATIVE` schedules that were created in the dashboard or using the imperative SDK functions like `schedules.create()`.

Delete Schedule

Deactivate a schedule by its ID. This will only work on `IMPERATIVE` schedules that were created in the dashboard or using the imperative SDK functions like `schedules.create()`.

Deactivate Schedule

Activate a schedule by its ID. This will only work on `IMPERATIVE` schedules that were created in the dashboard or using the imperative SDK functions like `schedules.create()`.

Activate Schedule

Get all supported timezones that schedule tasks support.

Get timezones

List all environment variables for a specific project and environment.

List Env Vars

Upload mulitple environment variables for a specific project and environment.

Import Env Vars

Create a new environment variable for a specific project and environment.

Create Env Var

Retrieve a specific environment variable for a specific project and environment.

Retrieve Env Var

Update a specific environment variable for a specific project and environment.

Update Env Var

Delete a specific environment variable for a specific project and environment.

Delete Env Var

List runs in a project, across multiple environments, using Personal Access Token auth. You can filter the runs by status, created at, task identifier, version, and more.

You can self-host Trigger.dev on your own infrastructure.

Self-hosting

You can contribute to Trigger.dev in many ways.

Contributing

GitHub repo

Some common problems you might experience and their solutions

Common problems

When we release fixes and new features we recommend you upgrade your Trigger.dev packages.

Upgrading packages

How to upgrade the Trigger.dev packages

Get alerted when runs or deployments fail, or when deployments succeed.

Alerts

Uptime Status

GitHub Issues

Request a feature

Discord Community

Slack support

Email us

This guide will show you how to setup Trigger.dev in your existing Node.js project, test an example task, and view the run.

Node.js

Node.js setup guide

This guide will show you how to setup Trigger.dev in your existing Next.js project, test an example task, and view the run.

Next.js

Next.js setup guide

This guide will show you how to setup Trigger.dev in your existing Remix project, test an example task, and view the run.

Getting Started

Fundamentals

Development

Deployment

Writing tasks

API reference

Open source

Troubleshooting

Help

List Schedules

Authorizations

Query Parameters

Response