Trigger.dev

PASS consensus from 3 PASS.

The quick start covers account creation, CLI initialization, Hello World, development mode, dashboard testing, and run confirmation. One page carries the whole path, npx trigger.dev@latest init, the Hello World example task, npx trigger.dev@latest dev, and the dashboard Test button, with the manual route split off to a separately labeled Manual setup page. The quick-start page names every command in order, init, dev, dashboard Test page, and the init command scaffolds the Hello World example task automatically.

PARTIAL consensus from 3 PARTIAL.

The limits page covers every category, but Triggering conflicts on payload and output caps. The Limits page gives per-plan numbers for concurrency, queue depth, API rate, batch buckets, retention, schedules, and alerts in one table set, but /docs/triggering states a 10MB payload limit and a 100MB output limit against the Limits page's 3MB and 10MB. The Limits page gives per-plan numbers for concurrency, queue depth, API rate, batch buckets, retention, schedules, and alerts in one table set, but the pricing FAQ contradicts the Pro concurrency limit (100+ vs 200) and the triggering page gives a different single-payload cap (3MB vs 10MB).

PASS consensus from 3 PASS.

The SDK exposes isRateLimited and retryAfterMs, and its bounded example waits before retrying or rethrows other errors. The condition is a typed error with isRateLimited and retryAfterMs, the correction is a working retry loop that sleeps for retryAfterMs, and the token-bucket sizes and refill rates are tabled per plan on the Limits page.

PASS consensus from 3 PASS.

The alert guide covers creation, run-failure selection, alert.run.failed, secret lookup, verification, and invalid-signature handling. Creation, the alert.run.failed switch case, webhooks.constructEvent with the secret, WebhookError handling, and the full run-failure payload schema are all on one page, though constructEvent appears nowhere else in the docs and has no reference entry. The alerts page documents creation, the alert.run.failed event type, the full payload schema, and tells you to use the SDK to parse the webhook. The SDK's webhooks.constructEvent() pattern is the natural completion, though constructEvent has no dedicated reference page.

PASS consensus from 2 PASS, 1 PARTIAL.

The SDK form is clear, but Tasks Overview imports helloWorld after defining it without export. @trigger.dev/sdk is named consistently across quick start, manual setup, tasks overview, and the management API, and the task({ id, run }) form is identical in every example. @trigger.dev/sdk is the single package name across quick start, manual setup, tasks overview, and triggering pages, and the task({ id, run }) form is identical in every code example.