github-featured/triggerdotdev--trigger.dev

Files

T

nicktrn 35c56f1d09 feat(supervisor): add opt-in dequeue backpressure (#3836 )

The supervisor can now pause dequeuing - and freeze consumer-pool
scale-up - when a backpressure signal says the cluster can't place more
work, then ramp dequeuing back up gradually once it clears. The signal
is a verdict published to a Redis key by a cluster-side component; the
supervisor reads it on a short refresh and gates `preDequeue` on it.

Off by default (`TRIGGER_DEQUEUE_BACKPRESSURE_ENABLED`). Everything
fails open: a missing, stale, or unreadable verdict never pins the
brake, and the hot-path read is a synchronous cached lookup with no I/O.
The scale-up freeze leaves scale-down untouched, and on release the
resume is ramped so a deep queue isn't hammered all at once.

Dry-run is on by default (`TRIGGER_DEQUEUE_BACKPRESSURE_DRY_RUN`): even
once enabled it only logs what it would have done, and surfaces the
computed state through metrics, until explicitly set to act. Prometheus:
`supervisor_backpressure_engaged`, `_dry_run`,
`_skipped_dequeues_total`.

Refs TRI-5354

2026-06-05 13:58:19 +01:00

src

feat(supervisor): add opt-in dequeue backpressure (#3836 )

2026-06-05 13:58:19 +01:00

.env.example

Fix: fixes and prerequisites for v4 self-hosting (#2150 )

2025-06-04 18:02:38 +01:00

.nvmrc

fix(repo): undo node.js supervisor upgrades and use the multiplatform node.js digest in Dockerfile (#2895 )

2026-01-15 11:49:37 +00:00

CLAUDE.md

chore(claude): Improve claude code instructions (#3161 )

2026-03-02 12:42:05 +00:00

Containerfile

chore: upgrade pnpm to 10.33.2 with security hardening (#3489 )

2026-05-01 16:24:26 +01:00

package.json

feat(supervisor): add opt-in dequeue backpressure (#3836 )

2026-06-05 13:58:19 +01:00

README.md

Allow self-hosted deploys locally by pointing to docker.host.internal on macOS (#2064 )

2025-05-16 15:20:48 +01:00

tsconfig.json

re2: env based queue selection algo (#1775 )

2025-03-07 14:30:19 +00:00

README.md

Supervisor

Dev setup

Create a worker group

api_url=http://localhost:3030
wg_name=my-worker

# edit this
admin_pat=tr_pat_...

curl -sS \
    -X POST \
    "$api_url/admin/api/v1/workers" \
    -H "Authorization: Bearer $admin_pat" \
    -H "Content-Type: application/json" \
    -d "{\"name\": \"$wg_name\"}"

If the worker group is newly created, the response will include a token field. If the group already exists, no token is returned.

Create .env and set the worker token

cp .env.example .env

# Then edit your .env and set this to the token.plaintext value
TRIGGER_WORKER_TOKEN=tr_wgt_...

Start the supervisor

pnpm dev

Build CLI, then deploy a test project

pnpm exec trigger deploy --self-hosted

# The additional network flag is required on linux
pnpm exec trigger deploy --self-hosted --network host

Worker group management

Shared variables

api_url=http://localhost:3030
admin_pat=tr_pat_... # edit this

These are used by all commands

Create a worker group

wg_name=my-worker

curl -sS \
    -X POST \
    "$api_url/admin/api/v1/workers" \
    -H "Authorization: Bearer $admin_pat" \
    -H "Content-Type: application/json" \
    -d "{\"name\": \"$wg_name\"}"

If the worker group already exists, no token will be returned

Set a worker group as default for a project

wg_name=my-worker
project_id=clsw6q8wz...

curl -sS \
    -X POST \
    "$api_url/admin/api/v1/workers" \
    -H "Authorization: Bearer $admin_pat" \
    -H "Content-Type: application/json" \
    -d "{\"name\": \"$wg_name\", \"projectId\": \"$project_id\", \"makeDefaultForProject\": true}"

If the worker group doesn't exist, yet it will be created
If the worker group already exists, it will be attached to the project as default. No token will be returned.

Remove the default worker group from a project

project_id=clsw6q8wz...

curl -sS \
    -X POST \
    "$api_url/admin/api/v1/workers" \
    -H "Authorization: Bearer $admin_pat" \
    -H "Content-Type: application/json" \
    -d "{\"projectId\": \"$project_id\", \"removeDefaultFromProject\": true}"

The project will then use the global default again
When removeDefaultFromProject: true no other actions will be performed