Skip to content

feat(webapp): gracefully shut down the v3 engine behind a flag#4017

Open
ericallam wants to merge 1 commit into
mainfrom
feat/v3-engine-shutdown
Open

feat(webapp): gracefully shut down the v3 engine behind a flag#4017
ericallam wants to merge 1 commit into
mainfrom
feat/v3-engine-shutdown

Conversation

@ericallam

Copy link
Copy Markdown
Member

Summary

Adds a single env flag, DEPRECATE_V3_ENABLED (default off), that gracefully winds down the v3 engine (RunEngineVersion.V1). While it's off nothing changes, so self-hosted instances still on v3 keep working. When it's on:

  • Triggers that resolve to v3 are rejected with a clear, actionable error pointing at the v4 migration guide, instead of silently creating runs that never execute. This covers single triggers, batches, scheduled fires, replays, and triggerAndWait, which all funnel through one place.
  • The legacy trigger dev websocket used by v3 CLIs is closed with an upgrade message (v4 CLIs use a different dev transport).
  • The v3 shared-queue consumer refuses to start, so no deployed v3 runs are dequeued.
  • The v3 run-lifecycle background jobs (heartbeat timeout, TTL expiry, retry, resume batch/dependency, delayed-run enqueue, and scheduled fires) become no-ops, so abandoned v3 runs stop generating database load.

This builds on the existing deploy deprecation flag, which already rejects v3 CLI deploys.

Design

Enforcement is read through one helper, isV3Disabled(). Every gate combines it with a per-run or per-project engine check (isV3Disabled() && engine === "V1"), so a v4 run that happens to reach a shared service behaves exactly as before. v4 (V2) is never affected.

The flag is a hard switch, not a drain: when it's on, in-flight v3 runs are abandoned in place rather than failed or expired, which is the intended behaviour for the final shutdown.

Adds DEPRECATE_V3_ENABLED (default off). When on, triggers that resolve to
v3 are rejected with a message pointing at the v4 migration guide, the
legacy dev websocket is closed, the v3 shared-queue consumer won't start,
and the v3 run-lifecycle background jobs (heartbeat timeout, TTL expiry,
retry, resume, delayed-run enqueue, scheduled fires) become no-ops so
abandoned v3 runs stop generating database load. Every gate also checks the
run or project is v3, so v4 is unaffected.
@changeset-bot

changeset-bot Bot commented Jun 22, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 3c1f9fa

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai

coderabbitai Bot commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 12adf4cf-2f4b-4f7e-a453-72e4c31a9ad3

📥 Commits

Reviewing files that changed from the base of the PR and between a90a495 and 3c1f9fa.

📒 Files selected for processing (13)
  • .server-changes/v3-engine-retirement-messaging.md
  • apps/webapp/app/env.server.ts
  • apps/webapp/app/v3/engineDeprecation.server.ts
  • apps/webapp/app/v3/handleSocketIo.server.ts
  • apps/webapp/app/v3/handleWebsockets.server.ts
  • apps/webapp/app/v3/scheduleEngine.server.ts
  • apps/webapp/app/v3/services/enqueueDelayedRun.server.ts
  • apps/webapp/app/v3/services/expireEnqueuedRun.server.ts
  • apps/webapp/app/v3/services/resumeBatchRun.server.ts
  • apps/webapp/app/v3/services/resumeTaskDependency.server.ts
  • apps/webapp/app/v3/services/retryAttempt.server.ts
  • apps/webapp/app/v3/services/triggerTask.server.ts
  • apps/webapp/app/v3/taskRunHeartbeatFailed.server.ts
📜 Recent review details
⏰ Context from checks skipped due to timeout. (12)
  • GitHub Check: webapp / 🧪 Unit Tests: Webapp (6, 10)
  • GitHub Check: webapp / 🧪 Unit Tests: Webapp (9, 10)
  • GitHub Check: webapp / 🧪 Unit Tests: Webapp (7, 10)
  • GitHub Check: webapp / 🧪 Unit Tests: Webapp (5, 10)
  • GitHub Check: webapp / 🧪 Unit Tests: Webapp (8, 10)
  • GitHub Check: webapp / 🧪 Unit Tests: Webapp (10, 10)
  • GitHub Check: webapp / 🧪 Unit Tests: Webapp (2, 10)
  • GitHub Check: webapp / 🧪 Unit Tests: Webapp (4, 10)
  • GitHub Check: webapp / 🧪 Unit Tests: Webapp (3, 10)
  • GitHub Check: webapp / 🧪 Unit Tests: Webapp (1, 10)
  • GitHub Check: typecheck / typecheck
  • GitHub Check: e2e-webapp / 🧪 E2E Tests: Webapp
🧰 Additional context used
📓 Path-based instructions (8)
**/*.{ts,tsx}

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

**/*.{ts,tsx}: Use types over interfaces for TypeScript
Avoid using enums; prefer string unions or const objects instead

Import from @trigger.dev/sdk when writing Trigger.dev tasks. Never use @trigger.dev/sdk/v3 or deprecated client.defineJob

Files:

  • apps/webapp/app/v3/services/resumeTaskDependency.server.ts
  • apps/webapp/app/v3/services/expireEnqueuedRun.server.ts
  • apps/webapp/app/v3/taskRunHeartbeatFailed.server.ts
  • apps/webapp/app/v3/services/triggerTask.server.ts
  • apps/webapp/app/v3/scheduleEngine.server.ts
  • apps/webapp/app/v3/services/resumeBatchRun.server.ts
  • apps/webapp/app/v3/handleSocketIo.server.ts
  • apps/webapp/app/v3/engineDeprecation.server.ts
  • apps/webapp/app/v3/services/enqueueDelayedRun.server.ts
  • apps/webapp/app/env.server.ts
  • apps/webapp/app/v3/handleWebsockets.server.ts
  • apps/webapp/app/v3/services/retryAttempt.server.ts
{packages/core,apps/webapp}/**/*.{ts,tsx}

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

Use zod for validation in packages/core and apps/webapp

Files:

  • apps/webapp/app/v3/services/resumeTaskDependency.server.ts
  • apps/webapp/app/v3/services/expireEnqueuedRun.server.ts
  • apps/webapp/app/v3/taskRunHeartbeatFailed.server.ts
  • apps/webapp/app/v3/services/triggerTask.server.ts
  • apps/webapp/app/v3/scheduleEngine.server.ts
  • apps/webapp/app/v3/services/resumeBatchRun.server.ts
  • apps/webapp/app/v3/handleSocketIo.server.ts
  • apps/webapp/app/v3/engineDeprecation.server.ts
  • apps/webapp/app/v3/services/enqueueDelayedRun.server.ts
  • apps/webapp/app/env.server.ts
  • apps/webapp/app/v3/handleWebsockets.server.ts
  • apps/webapp/app/v3/services/retryAttempt.server.ts
**/*.{ts,tsx,js,jsx}

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

Use function declarations instead of default exports

**/*.{ts,tsx,js,jsx}: Prefer static imports over dynamic imports. Only use dynamic import() when circular dependencies cannot be resolved, code splitting is needed for performance, or the module must be loaded conditionally at runtime
Import subpaths only from packages/core (@trigger.dev/core), never import from the root

Files:

  • apps/webapp/app/v3/services/resumeTaskDependency.server.ts
  • apps/webapp/app/v3/services/expireEnqueuedRun.server.ts
  • apps/webapp/app/v3/taskRunHeartbeatFailed.server.ts
  • apps/webapp/app/v3/services/triggerTask.server.ts
  • apps/webapp/app/v3/scheduleEngine.server.ts
  • apps/webapp/app/v3/services/resumeBatchRun.server.ts
  • apps/webapp/app/v3/handleSocketIo.server.ts
  • apps/webapp/app/v3/engineDeprecation.server.ts
  • apps/webapp/app/v3/services/enqueueDelayedRun.server.ts
  • apps/webapp/app/env.server.ts
  • apps/webapp/app/v3/handleWebsockets.server.ts
  • apps/webapp/app/v3/services/retryAttempt.server.ts
**/*.ts

📄 CodeRabbit inference engine (.cursor/rules/otel-metrics.mdc)

**/*.ts: When creating or editing OTEL metrics (counters, histograms, gauges), ensure metric attributes have low cardinality by using only enums, booleans, bounded error codes, or bounded shard IDs
Do not use high-cardinality attributes in OTEL metrics such as UUIDs/IDs (envId, userId, runId, projectId, organizationId), unbounded integers (itemCount, batchSize, retryCount), timestamps (createdAt, startTime), or free-form strings (errorMessage, taskName, queueName)
When exporting OTEL metrics via OTLP to Prometheus, be aware that the exporter automatically adds unit suffixes to metric names (e.g., 'my_duration_ms' becomes 'my_duration_ms_milliseconds', 'my_counter' becomes 'my_counter_total'). Account for these transformations when writing Grafana dashboards or Prometheus queries

Files:

  • apps/webapp/app/v3/services/resumeTaskDependency.server.ts
  • apps/webapp/app/v3/services/expireEnqueuedRun.server.ts
  • apps/webapp/app/v3/taskRunHeartbeatFailed.server.ts
  • apps/webapp/app/v3/services/triggerTask.server.ts
  • apps/webapp/app/v3/scheduleEngine.server.ts
  • apps/webapp/app/v3/services/resumeBatchRun.server.ts
  • apps/webapp/app/v3/handleSocketIo.server.ts
  • apps/webapp/app/v3/engineDeprecation.server.ts
  • apps/webapp/app/v3/services/enqueueDelayedRun.server.ts
  • apps/webapp/app/env.server.ts
  • apps/webapp/app/v3/handleWebsockets.server.ts
  • apps/webapp/app/v3/services/retryAttempt.server.ts
apps/webapp/**/*.{ts,tsx}

📄 CodeRabbit inference engine (.cursor/rules/webapp.mdc)

apps/webapp/**/*.{ts,tsx}: Access environment variables through the env export of env.server.ts instead of directly accessing process.env
Use subpath exports from @trigger.dev/core package instead of importing from the root @trigger.dev/core path

Use named constants for sentinel/placeholder values (e.g. const UNSET_VALUE = '__unset__') instead of raw string literals scattered across comparisons

Files:

  • apps/webapp/app/v3/services/resumeTaskDependency.server.ts
  • apps/webapp/app/v3/services/expireEnqueuedRun.server.ts
  • apps/webapp/app/v3/taskRunHeartbeatFailed.server.ts
  • apps/webapp/app/v3/services/triggerTask.server.ts
  • apps/webapp/app/v3/scheduleEngine.server.ts
  • apps/webapp/app/v3/services/resumeBatchRun.server.ts
  • apps/webapp/app/v3/handleSocketIo.server.ts
  • apps/webapp/app/v3/engineDeprecation.server.ts
  • apps/webapp/app/v3/services/enqueueDelayedRun.server.ts
  • apps/webapp/app/env.server.ts
  • apps/webapp/app/v3/handleWebsockets.server.ts
  • apps/webapp/app/v3/services/retryAttempt.server.ts
apps/webapp/**/*.server.ts

📄 CodeRabbit inference engine (apps/webapp/CLAUDE.md)

apps/webapp/**/*.server.ts: Never use request.signal for detecting client disconnects. Use getRequestAbortSignal() from app/services/httpAsyncStorage.server.ts instead, which is wired directly to Express res.on('close') and fires reliably
Access environment variables via env export from app/env.server.ts. Never use process.env directly
Always use findFirst instead of findUnique in Prisma queries. findUnique has an implicit DataLoader that batches concurrent calls and has active bugs even in Prisma 6.x (uppercase UUIDs returning null, composite key SQL correctness issues, 5-10x worse performance). findFirst is never batched and avoids this entire class of issues

Files:

  • apps/webapp/app/v3/services/resumeTaskDependency.server.ts
  • apps/webapp/app/v3/services/expireEnqueuedRun.server.ts
  • apps/webapp/app/v3/taskRunHeartbeatFailed.server.ts
  • apps/webapp/app/v3/services/triggerTask.server.ts
  • apps/webapp/app/v3/scheduleEngine.server.ts
  • apps/webapp/app/v3/services/resumeBatchRun.server.ts
  • apps/webapp/app/v3/handleSocketIo.server.ts
  • apps/webapp/app/v3/engineDeprecation.server.ts
  • apps/webapp/app/v3/services/enqueueDelayedRun.server.ts
  • apps/webapp/app/env.server.ts
  • apps/webapp/app/v3/handleWebsockets.server.ts
  • apps/webapp/app/v3/services/retryAttempt.server.ts
**/*.{js,ts,tsx,jsx,css,json,md}

📄 CodeRabbit inference engine (AGENTS.md)

Use Prettier for code formatting and run pnpm run format before committing

Files:

  • apps/webapp/app/v3/services/resumeTaskDependency.server.ts
  • apps/webapp/app/v3/services/expireEnqueuedRun.server.ts
  • apps/webapp/app/v3/taskRunHeartbeatFailed.server.ts
  • apps/webapp/app/v3/services/triggerTask.server.ts
  • apps/webapp/app/v3/scheduleEngine.server.ts
  • apps/webapp/app/v3/services/resumeBatchRun.server.ts
  • apps/webapp/app/v3/handleSocketIo.server.ts
  • apps/webapp/app/v3/engineDeprecation.server.ts
  • apps/webapp/app/v3/services/enqueueDelayedRun.server.ts
  • apps/webapp/app/env.server.ts
  • apps/webapp/app/v3/handleWebsockets.server.ts
  • apps/webapp/app/v3/services/retryAttempt.server.ts
apps/webapp/{app/v3/services/triggerTask.server.ts,app/v3/services/batchTriggerV3.server.ts}

📄 CodeRabbit inference engine (apps/webapp/CLAUDE.md)

In triggerTask.server.ts and batchTriggerV3.server.ts, do NOT add database queries. Task defaults (TTL, etc.) are resolved via backgroundWorkerTask.findFirst() in the queue concern (queues.server.ts). Piggyback on the existing query instead of adding new ones

Files:

  • apps/webapp/app/v3/services/triggerTask.server.ts
🧠 Learnings (17)
📚 Learning: 2026-03-10T17:56:20.938Z
Learnt from: samejr
Repo: triggerdotdev/trigger.dev PR: 3201
File: apps/webapp/app/v3/services/setSeatsAddOn.server.ts:25-29
Timestamp: 2026-03-10T17:56:20.938Z
Learning: Do not implement local userId-to-organizationId authorization checks inside org-scoped service classes (e.g., SetSeatsAddOnService, SetBranchesAddOnService) in the web app. Rely on route-layer authentication (requireUserId(request)) and org membership enforcement via the _app.orgs.$organizationSlug layout route. Any userId/organizationId that reaches these services from org-scoped routes has already been validated. Apply this pattern across all org-scoped services to avoid redundant auth checks and maintain consistency.

Applied to files:

  • apps/webapp/app/v3/services/resumeTaskDependency.server.ts
  • apps/webapp/app/v3/services/expireEnqueuedRun.server.ts
  • apps/webapp/app/v3/services/triggerTask.server.ts
  • apps/webapp/app/v3/services/resumeBatchRun.server.ts
  • apps/webapp/app/v3/services/enqueueDelayedRun.server.ts
  • apps/webapp/app/v3/services/retryAttempt.server.ts
📚 Learning: 2026-03-22T13:26:12.060Z
Learnt from: ericallam
Repo: triggerdotdev/trigger.dev PR: 3244
File: apps/webapp/app/components/code/TextEditor.tsx:81-86
Timestamp: 2026-03-22T13:26:12.060Z
Learning: In the triggerdotdev/trigger.dev codebase, do not flag `navigator.clipboard.writeText(...)` calls for `missing-await`/`unhandled-promise` issues. These clipboard writes are intentionally invoked without `await` and without `catch` handlers across the project; keep that behavior consistent when reviewing TypeScript/TSX files (e.g., usages like in `apps/webapp/app/components/code/TextEditor.tsx`).

Applied to files:

  • apps/webapp/app/v3/services/resumeTaskDependency.server.ts
  • apps/webapp/app/v3/services/expireEnqueuedRun.server.ts
  • apps/webapp/app/v3/taskRunHeartbeatFailed.server.ts
  • apps/webapp/app/v3/services/triggerTask.server.ts
  • apps/webapp/app/v3/scheduleEngine.server.ts
  • apps/webapp/app/v3/services/resumeBatchRun.server.ts
  • apps/webapp/app/v3/handleSocketIo.server.ts
  • apps/webapp/app/v3/engineDeprecation.server.ts
  • apps/webapp/app/v3/services/enqueueDelayedRun.server.ts
  • apps/webapp/app/env.server.ts
  • apps/webapp/app/v3/handleWebsockets.server.ts
  • apps/webapp/app/v3/services/retryAttempt.server.ts
📚 Learning: 2026-03-22T19:24:14.403Z
Learnt from: matt-aitken
Repo: triggerdotdev/trigger.dev PR: 3187
File: apps/webapp/app/v3/services/alerts/deliverErrorGroupAlert.server.ts:200-204
Timestamp: 2026-03-22T19:24:14.403Z
Learning: In the triggerdotdev/trigger.dev codebase, webhook URLs are not expected to contain embedded credentials/secrets (e.g., fields like `ProjectAlertWebhookProperties` should only hold credential-free webhook endpoints). During code review, if you see logging or inclusion of raw webhook URLs in error messages, do not automatically treat it as a credential-leak/secrets-in-logs issue by default—first verify the URL does not contain embedded credentials (for example, no username/password in the URL, no obvious secret/token query params or fragments). If the URL is credential-free per this project’s conventions, allow the logging.

Applied to files:

  • apps/webapp/app/v3/services/resumeTaskDependency.server.ts
  • apps/webapp/app/v3/services/expireEnqueuedRun.server.ts
  • apps/webapp/app/v3/taskRunHeartbeatFailed.server.ts
  • apps/webapp/app/v3/services/triggerTask.server.ts
  • apps/webapp/app/v3/scheduleEngine.server.ts
  • apps/webapp/app/v3/services/resumeBatchRun.server.ts
  • apps/webapp/app/v3/handleSocketIo.server.ts
  • apps/webapp/app/v3/engineDeprecation.server.ts
  • apps/webapp/app/v3/services/enqueueDelayedRun.server.ts
  • apps/webapp/app/env.server.ts
  • apps/webapp/app/v3/handleWebsockets.server.ts
  • apps/webapp/app/v3/services/retryAttempt.server.ts
📚 Learning: 2026-05-18T08:21:27.694Z
Learnt from: d-cs
Repo: triggerdotdev/trigger.dev PR: 3632
File: apps/webapp/sentry.server.ts:4-21
Timestamp: 2026-05-18T08:21:27.694Z
Learning: When handling Prisma error P1001 ("Can't reach database server") in TypeScript, don’t assume a single error shape. Prisma can surface P1001 via two different error classes/fields: `PrismaClientKnownRequestError` exposes it as `err.code === "P1001"` (common during mid-query connection drops), while `PrismaClientInitializationError` exposes it as `err.errorCode === "P1001"` (common on client startup failure). Therefore, predicates should use `err.code === "P1001" || err.errorCode === "P1001"`. Do not flag `err.code === "P1001"` as “unreachable/never matches,” as it is expected in production.

Applied to files:

  • apps/webapp/app/v3/services/resumeTaskDependency.server.ts
  • apps/webapp/app/v3/services/expireEnqueuedRun.server.ts
  • apps/webapp/app/v3/taskRunHeartbeatFailed.server.ts
  • apps/webapp/app/v3/services/triggerTask.server.ts
  • apps/webapp/app/v3/scheduleEngine.server.ts
  • apps/webapp/app/v3/services/resumeBatchRun.server.ts
  • apps/webapp/app/v3/handleSocketIo.server.ts
  • apps/webapp/app/v3/engineDeprecation.server.ts
  • apps/webapp/app/v3/services/enqueueDelayedRun.server.ts
  • apps/webapp/app/env.server.ts
  • apps/webapp/app/v3/handleWebsockets.server.ts
  • apps/webapp/app/v3/services/retryAttempt.server.ts
📚 Learning: 2026-05-18T08:21:27.694Z
Learnt from: d-cs
Repo: triggerdotdev/trigger.dev PR: 3632
File: apps/webapp/sentry.server.ts:4-21
Timestamp: 2026-05-18T08:21:27.694Z
Learning: When handling Prisma errors for P1001 ("Can't reach database server"), do not assume it only appears under a single property name. Prisma may surface P1001 via either `PrismaClientKnownRequestError` (`err.code === "P1001"`, e.g., mid-query connection drops) or `PrismaClientInitializationError` (`err.errorCode === "P1001"`, e.g., client startup connection failure). To reliably detect the condition, check `err.code === "P1001" || err.errorCode === "P1001"`, and avoid review rules that would incorrectly flag `err.code === "P1001"` as unreachable/never-matching.

Applied to files:

  • apps/webapp/app/v3/services/resumeTaskDependency.server.ts
  • apps/webapp/app/v3/services/expireEnqueuedRun.server.ts
  • apps/webapp/app/v3/taskRunHeartbeatFailed.server.ts
  • apps/webapp/app/v3/services/triggerTask.server.ts
  • apps/webapp/app/v3/scheduleEngine.server.ts
  • apps/webapp/app/v3/services/resumeBatchRun.server.ts
  • apps/webapp/app/v3/handleSocketIo.server.ts
  • apps/webapp/app/v3/engineDeprecation.server.ts
  • apps/webapp/app/v3/services/enqueueDelayedRun.server.ts
  • apps/webapp/app/env.server.ts
  • apps/webapp/app/v3/handleWebsockets.server.ts
  • apps/webapp/app/v3/services/retryAttempt.server.ts
📚 Learning: 2026-06-13T19:53:13.759Z
Learnt from: ericallam
Repo: triggerdotdev/trigger.dev PR: 3937
File: packages/trigger-sdk/skills/realtime-and-frontend/SKILL.md:258-260
Timestamp: 2026-06-13T19:53:13.759Z
Learning: When reviewing code that uses `trigger.dev/react-hooks`’s `useRealtimeRun`, preserve the call signature where the first argument is the full realtime handle object (not `handle.id`). This is intentional to maintain type-safety and is consistent with the official docs; do not suggest changing the first argument from the handle object to `handle.id`.

Applied to files:

  • apps/webapp/app/v3/services/resumeTaskDependency.server.ts
  • apps/webapp/app/v3/services/expireEnqueuedRun.server.ts
  • apps/webapp/app/v3/taskRunHeartbeatFailed.server.ts
  • apps/webapp/app/v3/services/triggerTask.server.ts
  • apps/webapp/app/v3/scheduleEngine.server.ts
  • apps/webapp/app/v3/services/resumeBatchRun.server.ts
  • apps/webapp/app/v3/handleSocketIo.server.ts
  • apps/webapp/app/v3/engineDeprecation.server.ts
  • apps/webapp/app/v3/services/enqueueDelayedRun.server.ts
  • apps/webapp/app/env.server.ts
  • apps/webapp/app/v3/handleWebsockets.server.ts
  • apps/webapp/app/v3/services/retryAttempt.server.ts
📚 Learning: 2026-06-17T17:13:49.929Z
Learnt from: matt-aitken
Repo: triggerdotdev/trigger.dev PR: 3948
File: apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.bulk-actions.$bulkActionParam/route.tsx:48-62
Timestamp: 2026-06-17T17:13:49.929Z
Learning: In triggerdotdev/trigger.dev, within `dashboardLoader`/`dashboardAction` (or similar context resolver code) whenever you resolve an organization ID from an organization slug for RBAC/enterprise authorization scope, always read from the primary Prisma client (`prisma`), not `$replica`. Using `$replica` can hit replica-lag and cause the RBAC lookup/authorization to run without the correct org scope (bypassing intended role enforcement). Implement the slug→org lookup with `prisma.organization.findFirst(...)` (or equivalent primary-client query) and add an inline comment documenting why the primary client is required (replica lag could lead to unscoped RBAC checks).

Applied to files:

  • apps/webapp/app/v3/services/resumeTaskDependency.server.ts
  • apps/webapp/app/v3/services/expireEnqueuedRun.server.ts
  • apps/webapp/app/v3/taskRunHeartbeatFailed.server.ts
  • apps/webapp/app/v3/services/triggerTask.server.ts
  • apps/webapp/app/v3/scheduleEngine.server.ts
  • apps/webapp/app/v3/services/resumeBatchRun.server.ts
  • apps/webapp/app/v3/handleSocketIo.server.ts
  • apps/webapp/app/v3/engineDeprecation.server.ts
  • apps/webapp/app/v3/services/enqueueDelayedRun.server.ts
  • apps/webapp/app/env.server.ts
  • apps/webapp/app/v3/handleWebsockets.server.ts
  • apps/webapp/app/v3/services/retryAttempt.server.ts
📚 Learning: 2026-03-29T19:16:28.864Z
Learnt from: nicktrn
Repo: triggerdotdev/trigger.dev PR: 3291
File: apps/webapp/app/v3/featureFlags.ts:53-65
Timestamp: 2026-03-29T19:16:28.864Z
Learning: When reviewing TypeScript code that uses Zod v3, treat `z.coerce.*()` schemas as their direct Zod type (e.g., `z.coerce.boolean()` returns a `ZodBoolean` with `_def.typeName === "ZodBoolean"`) rather than a `ZodEffects`. Only `.preprocess()`, `.refine()`/`.superRefine()`, and `.transform()` are expected to wrap schemas in `ZodEffects`. Therefore, in reviewers’ logic like `getFlagControlType`, do not flag/unblock failures that require unwrapping `ZodEffects` when the input schema is a `z.coerce.*` schema.

Applied to files:

  • apps/webapp/app/v3/services/resumeTaskDependency.server.ts
  • apps/webapp/app/v3/services/expireEnqueuedRun.server.ts
  • apps/webapp/app/v3/taskRunHeartbeatFailed.server.ts
  • apps/webapp/app/v3/services/triggerTask.server.ts
  • apps/webapp/app/v3/scheduleEngine.server.ts
  • apps/webapp/app/v3/services/resumeBatchRun.server.ts
  • apps/webapp/app/v3/handleSocketIo.server.ts
  • apps/webapp/app/v3/engineDeprecation.server.ts
  • apps/webapp/app/v3/services/enqueueDelayedRun.server.ts
  • apps/webapp/app/v3/handleWebsockets.server.ts
  • apps/webapp/app/v3/services/retryAttempt.server.ts
📚 Learning: 2026-06-09T16:27:26.195Z
Learnt from: myftija
Repo: triggerdotdev/trigger.dev PR: 3878
File: apps/webapp/app/v3/services/computeTemplateCreation.server.ts:0-0
Timestamp: 2026-06-09T16:27:26.195Z
Learning: When working in triggerdotdev/trigger.dev code related to worker-group/region default resolution (e.g., defaultWorkerInstanceGroupId handling used by getGlobalDefaultWorkerGroup, getDefaultWorkerGroupForProject, and RegionsPresenter), do NOT add org-level featureFlags overrides in only one resolution site. That can cause template creation routing/decisions to diverge from actual run routing. If org-level override of the default region/worker group is required, it must be centralized in getGlobalDefaultWorkerGroup so every resolution path remains aligned.

Applied to files:

  • apps/webapp/app/v3/services/resumeTaskDependency.server.ts
  • apps/webapp/app/v3/services/expireEnqueuedRun.server.ts
  • apps/webapp/app/v3/taskRunHeartbeatFailed.server.ts
  • apps/webapp/app/v3/services/triggerTask.server.ts
  • apps/webapp/app/v3/scheduleEngine.server.ts
  • apps/webapp/app/v3/services/resumeBatchRun.server.ts
  • apps/webapp/app/v3/handleSocketIo.server.ts
  • apps/webapp/app/v3/engineDeprecation.server.ts
  • apps/webapp/app/v3/services/enqueueDelayedRun.server.ts
  • apps/webapp/app/v3/handleWebsockets.server.ts
  • apps/webapp/app/v3/services/retryAttempt.server.ts
📚 Learning: 2026-05-05T09:38:02.512Z
Learnt from: d-cs
Repo: triggerdotdev/trigger.dev PR: 3523
File: apps/webapp/app/routes/api.v3.batches.ts:178-181
Timestamp: 2026-05-05T09:38:02.512Z
Learning: When reviewing code that catches `ServiceValidationError` in `*.server.ts` files, do not blindly forward `error.status` to HTTP responses, because SVEs may be thrown with non-default statuses (e.g., 400/500) and forwarding them can cause client-visible behavioral regressions (e.g., surfacing 500s to clients). Prefer a safe default response status of `error.status ?? 422`, but only after confirming via the reachable call graph that the caught `ServiceValidationError` instances are expected to carry those non-default statuses; otherwise, normalize to `422` to avoid unexpected client-visible 5xx behavior.

Applied to files:

  • apps/webapp/app/v3/services/resumeTaskDependency.server.ts
  • apps/webapp/app/v3/services/expireEnqueuedRun.server.ts
  • apps/webapp/app/v3/taskRunHeartbeatFailed.server.ts
  • apps/webapp/app/v3/services/triggerTask.server.ts
  • apps/webapp/app/v3/scheduleEngine.server.ts
  • apps/webapp/app/v3/services/resumeBatchRun.server.ts
  • apps/webapp/app/v3/handleSocketIo.server.ts
  • apps/webapp/app/v3/engineDeprecation.server.ts
  • apps/webapp/app/v3/services/enqueueDelayedRun.server.ts
  • apps/webapp/app/env.server.ts
  • apps/webapp/app/v3/handleWebsockets.server.ts
  • apps/webapp/app/v3/services/retryAttempt.server.ts
📚 Learning: 2026-05-12T21:04:05.815Z
Learnt from: ericallam
Repo: triggerdotdev/trigger.dev PR: 3542
File: apps/webapp/app/components/sessions/v1/SessionStatus.tsx:1-3
Timestamp: 2026-05-12T21:04:05.815Z
Learning: In this Remix + TypeScript codebase, do not flag a server/client boundary violation when a file imports only types from a module matching `*.server`.

Specifically, it’s safe to import types using `import type { Foo } from "*.server"` or `import { type Foo } from "*.server"` because TypeScript erases type-only imports at compile time and they emit no JavaScript, so they won’t cross the Remix server/client bundle boundary.

Only raise the boundary concern for value imports (e.g., `import { Foo }` without `type`, or `import Foo`), since those produce JavaScript output.

Applied to files:

  • apps/webapp/app/v3/services/resumeTaskDependency.server.ts
  • apps/webapp/app/v3/services/expireEnqueuedRun.server.ts
  • apps/webapp/app/v3/taskRunHeartbeatFailed.server.ts
  • apps/webapp/app/v3/services/triggerTask.server.ts
  • apps/webapp/app/v3/scheduleEngine.server.ts
  • apps/webapp/app/v3/services/resumeBatchRun.server.ts
  • apps/webapp/app/v3/handleSocketIo.server.ts
  • apps/webapp/app/v3/engineDeprecation.server.ts
  • apps/webapp/app/v3/services/enqueueDelayedRun.server.ts
  • apps/webapp/app/env.server.ts
  • apps/webapp/app/v3/handleWebsockets.server.ts
  • apps/webapp/app/v3/services/retryAttempt.server.ts
📚 Learning: 2026-05-14T08:21:07.614Z
Learnt from: d-cs
Repo: triggerdotdev/trigger.dev PR: 3614
File: apps/webapp/app/v3/mollifier/mollifierGate.server.ts:48-52
Timestamp: 2026-05-14T08:21:07.614Z
Learning: When using Trigger.dev v3 feature flags in the webapp, prefer the existing per-org gating mechanism supported by `flag()` via the `overrides` argument. Pass `Organization.featureFlags` (from `environment.organization.featureFlags`) as the `overrides` value; overrides must take precedence over the global `featureFlag` row. Do not require schema changes or add an `orgId` field to `FlagsOptions` for per-org gating—use the overrides pattern consistently (e.g., in gate flows like `resolveOrgFlag` and any server code that threads `environment.organization.featureFlags` into the gate call).

Applied to files:

  • apps/webapp/app/v3/services/resumeTaskDependency.server.ts
  • apps/webapp/app/v3/services/expireEnqueuedRun.server.ts
  • apps/webapp/app/v3/taskRunHeartbeatFailed.server.ts
  • apps/webapp/app/v3/services/triggerTask.server.ts
  • apps/webapp/app/v3/scheduleEngine.server.ts
  • apps/webapp/app/v3/services/resumeBatchRun.server.ts
  • apps/webapp/app/v3/handleSocketIo.server.ts
  • apps/webapp/app/v3/engineDeprecation.server.ts
  • apps/webapp/app/v3/services/enqueueDelayedRun.server.ts
  • apps/webapp/app/v3/handleWebsockets.server.ts
  • apps/webapp/app/v3/services/retryAttempt.server.ts
📚 Learning: 2026-06-04T18:16:35.386Z
Learnt from: nicktrn
Repo: triggerdotdev/trigger.dev PR: 3836
File: apps/supervisor/src/backpressure/backpressureMonitor.ts:3-5
Timestamp: 2026-06-04T18:16:35.386Z
Learning: When reviewing TypeScript in this repo, apply the rule “prefer type aliases over interfaces” only to data/object shapes and union/intersection type modeling. If an interface is being used as a behavioral contract for collaborators to implement (e.g., method-shape interfaces that define required behavior, such as `BackpressureLogger` / `BackpressureSignalSource` in `apps/supervisor/src/backpressure/backpressureMonitor.ts`), keep it as an `interface` and do not flag it as a type-alias-vs-interface violation.

Applied to files:

  • apps/webapp/app/v3/services/resumeTaskDependency.server.ts
  • apps/webapp/app/v3/services/expireEnqueuedRun.server.ts
  • apps/webapp/app/v3/taskRunHeartbeatFailed.server.ts
  • apps/webapp/app/v3/services/triggerTask.server.ts
  • apps/webapp/app/v3/scheduleEngine.server.ts
  • apps/webapp/app/v3/services/resumeBatchRun.server.ts
  • apps/webapp/app/v3/handleSocketIo.server.ts
  • apps/webapp/app/v3/engineDeprecation.server.ts
  • apps/webapp/app/v3/services/enqueueDelayedRun.server.ts
  • apps/webapp/app/env.server.ts
  • apps/webapp/app/v3/handleWebsockets.server.ts
  • apps/webapp/app/v3/services/retryAttempt.server.ts
📚 Learning: 2026-06-09T17:58:04.699Z
Learnt from: 0ski
Repo: triggerdotdev/trigger.dev PR: 3879
File: apps/webapp/app/models/vercelIntegration.server.ts:619-630
Timestamp: 2026-06-09T17:58:04.699Z
Learning: In this codebase, outbound raw `fetch` calls should typically rely on Node/undici’s default request timeout (about ~300s) rather than adding a per-call `AbortController` + `setTimeout` wrapper inside individual functions (e.g. in files like `apps/webapp/app/models/vercelIntegration.server.ts`). During code review, do not flag the absence of a per-call timeout on a single `fetch` as an issue; if per-call timeouts are needed, they should be implemented via a codebase-wide convention (e.g., a shared fetch wrapper or documented pattern) rather than ad-hoc per-function changes.

Applied to files:

  • apps/webapp/app/v3/services/resumeTaskDependency.server.ts
  • apps/webapp/app/v3/services/expireEnqueuedRun.server.ts
  • apps/webapp/app/v3/taskRunHeartbeatFailed.server.ts
  • apps/webapp/app/v3/services/triggerTask.server.ts
  • apps/webapp/app/v3/scheduleEngine.server.ts
  • apps/webapp/app/v3/services/resumeBatchRun.server.ts
  • apps/webapp/app/v3/handleSocketIo.server.ts
  • apps/webapp/app/v3/engineDeprecation.server.ts
  • apps/webapp/app/v3/services/enqueueDelayedRun.server.ts
  • apps/webapp/app/env.server.ts
  • apps/webapp/app/v3/handleWebsockets.server.ts
  • apps/webapp/app/v3/services/retryAttempt.server.ts
📚 Learning: 2026-05-14T14:54:39.095Z
Learnt from: ericallam
Repo: triggerdotdev/trigger.dev PR: 3545
File: .server-changes/agent-view-sessions.md:10-10
Timestamp: 2026-05-14T14:54:39.095Z
Learning: In the `trigger.dev` repository, do not flag inconsistent dot vs slash notation in route/path strings inside `.server-changes/*.md` files. These markdown files are consumed verbatim into the changelog, so the mixed notation (e.g., `resources.orgs.../runs.$runParam/...`) is intentional and should be preserved as-is.

Applied to files:

  • .server-changes/v3-engine-retirement-messaging.md
📚 Learning: 2026-05-20T17:21:18.543Z
Learnt from: d-cs
Repo: triggerdotdev/trigger.dev PR: 3678
File: apps/webapp/app/entry.server.tsx:0-0
Timestamp: 2026-05-20T17:21:18.543Z
Learning: In env.server.ts (Zod env schema), any environment variable you plan to access via the typed `env` export (e.g., `env.SENTRY_DSN`) must be explicitly declared in the schema. For `SENTRY_DSN`, include `SENTRY_DSN: z.string().optional()`; otherwise switching from `process.env.SENTRY_DSN` to `env.SENTRY_DSN` will fail TypeScript typechecking.

Applied to files:

  • apps/webapp/app/env.server.ts
📚 Learning: 2026-06-01T11:37:08.569Z
Learnt from: d-cs
Repo: triggerdotdev/trigger.dev PR: 3754
File: apps/webapp/app/env.server.ts:1104-1129
Timestamp: 2026-06-01T11:37:08.569Z
Learning: In apps/*/app/env.server.ts, any new background/periodic worker feature flag should hard-default to "0" (explicit opt-in) rather than inheriting from a parent flag (e.g., avoid defaulting to process.env.TRIGGER_MOLLIFIER_ENABLED ?? "0"). Inheriting can cause the new worker to auto-start on upgrade for deployments that already enabled the parent flag, turning on unexpected background load without an explicit rollout. Each worker component must require its own dedicated env var and default it explicitly to "0" (e.g., TRIGGER_MOLLIFIER_STALE_SWEEP_ENABLED defaults to "0" unless explicitly set to enable that worker).

Applied to files:

  • apps/webapp/app/env.server.ts
🔇 Additional comments (13)
.server-changes/v3-engine-retirement-messaging.md (1)

1-7: LGTM!

apps/webapp/app/env.server.ts (1)

538-547: LGTM!

apps/webapp/app/v3/services/triggerTask.server.ts (1)

13-14: LGTM!

Also applies to: 81-88

apps/webapp/app/v3/scheduleEngine.server.ts (1)

13-13: LGTM!

Also applies to: 88-99

apps/webapp/app/v3/services/enqueueDelayedRun.server.ts (1)

8-8: LGTM!

Also applies to: 79-84

apps/webapp/app/v3/services/expireEnqueuedRun.server.ts (1)

8-8: LGTM!

Also applies to: 52-57

apps/webapp/app/v3/services/retryAttempt.server.ts (1)

5-5: LGTM!

Also applies to: 16-21

apps/webapp/app/v3/engineDeprecation.server.ts (1)

1-34: LGTM!

apps/webapp/app/v3/handleWebsockets.server.ts (1)

9-9: LGTM!

Also applies to: 62-74

apps/webapp/app/v3/handleSocketIo.server.ts (1)

39-39: LGTM!

Also applies to: 430-439

apps/webapp/app/v3/taskRunHeartbeatFailed.server.ts (1)

11-11: LGTM!

Also applies to: 22-22, 54-62

apps/webapp/app/v3/services/resumeBatchRun.server.ts (1)

8-8: LGTM!

Also applies to: 47-54

apps/webapp/app/v3/services/resumeTaskDependency.server.ts (1)

6-6: LGTM!

Also applies to: 36-43


Walkthrough

A new DEPRECATE_V3_ENABLED environment variable (default "0") is added to the server environment schema. A new engineDeprecation.server.ts module exports a migration URL, two user-facing deprecation messages, and an isV3Disabled() helper. When the flag is enabled, the legacy v3 dev CLI websocket handler closes connections with code 1008, the /shared-queue socket handler disconnects immediately, TriggerTaskService throws a ServiceValidationError for V1-routed tasks, and seven background lifecycle services (scheduled task firing, delayed run enqueueing, run expiry, retry scheduling, heartbeat failure handling, batch run resume, and task dependency resume) return early for V1 engine runs without performing their normal operations.

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name Status Explanation Resolution
Description check ⚠️ Warning The PR description thoroughly covers the feature, design rationale, and implementation details, but the description template sections (Checklist, Testing, Changelog, Screenshots) are not filled in. Complete all required template sections: confirm checklist items, describe testing steps performed, add changelog summary, and note screenshots if applicable.
Docstring Coverage ⚠️ Warning Docstring coverage is 25.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely summarizes the main change: introducing a flag-based graceful shutdown mechanism for the v3 engine.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/v3-engine-shutdown

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@ericallam ericallam marked this pull request as ready for review June 22, 2026 16:39

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Open in Devin Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants