Trigger.dev

Overview

Trigger.dev runs the slow, long or scheduled work your app should not do inside a web request: sending a batch of emails, processing a video, or running an AI agent for ten minutes. You write each job as a TypeScript function in your own codebase. This app is the control plane: it queues the runs, retries them when they fail, and shows every run, log line and trace in one dashboard.

Features

• Tasks written as plain async TypeScript functions, with no timeouts
• Automatic retries, queues and concurrency limits per task
• Scheduled tasks on a cron schedule, set in code or in the dashboard
• A live dashboard with every run, its logs, its trace and its payload
• Waits and human-in-the-loop steps: pause a run until a date or an approval
• Realtime run updates you can stream into your own front end
• Dev mode: run tasks on your own machine against this dashboard, with instant reload

Setting up

You sign in with your email address and a one-time link.

• With a mail provider bound to this app, the link arrives by email.
• Without one, open the Logs tab and look for sendEmail to <your address>. The sign-in link is just below it.

The same Logs tab shows the worker token once, on the very first start, in a block titled Trigger.dev Bootstrap - Worker Token. Copy it somewhere safe. You need it only if you run your own worker server (see below).

To run tasks from your project, install the CLI and log in to this app:

• npx trigger.dev@4.6.4 login -a <this app's address>
• npx trigger.dev@4.6.4 dev

Good to know

• Tasks do not run on this box. Trigger.dev starts each run in a fresh container, and moose does not let an app start containers. So you run your tasks on a computer you control. trigger dev runs them on your own machine, which is how you build and test. For deployed tasks and schedules that run while your laptop is off, you run Trigger.dev's worker on your own Docker server, pointed at this app. Its setup needs the worker token above and the Managed worker secret shown on this app's page in moose.
• Deploys go to your own image registry. trigger deploy builds an image and pushes it to a registry such as Docker Hub or GitHub, set in this app's settings. Your worker server pulls it from there.
• This is a heavy app. It runs the web app, its own Postgres, a ClickHouse analytics database, an object store and a sync service, alongside moose's managed cache. Plan for a few gigabytes of memory.
• Email is off until you connect a mail provider. Sign-in still works through the Logs tab. Invites and alert emails are not sent.