Trigger.dev v4.4.3

2 improvements and 2 server changes.

Improvements

• syncSupabaseEnvVars pulls your Supabase project's database connection strings and saves them as Trigger.dev environment variables, removing the manual copy-paste step when setting up Supabase-connected tasks. (docs, #3152)

  
  

  // trigger.config.ts

  import { defineConfig } from "@trigger.dev/sdk";

  import { syncSupabaseEnvVars } from "@trigger.dev/build/extensions/core";

  export default defineConfig({

  build: {

  extensions: [syncSupabaseEnvVars()],

  },

  });

  
  

• Auto-cancel in-flight dev runs when the CLI exits, using a detached watchdog process that survives pnpm SIGKILL. (#3191)

Server changes

These changes are included in the v4.4.3 Docker image and are already live on Trigger.dev Cloud:

• New Errors page for viewing and tracking run failures. Errors are grouped by fingerprint — view top errors for a time period, filter by task, search by text, and see occurrences over time. From the error detail view you can list all affected runs and bulk replay them. (#3172)

  Private alpha on Trigger.dev Cloud — The Errors page is available now for self-hosted users. On Trigger.dev Cloud it's currently in private alpha, with a full public release coming soon. Contact us to get early access.

• The Test page now lets you automatically generate example payloads using AI. For schemaTask tasks, the AI uses your task's JSON schema to generate valid payloads. For regular tasks, it infers the schema from previous run payloads. The new sidebar tabs (Options, AI, Schema) give you full visibility into the schema being used. (#3188)

How to upgrade

Update the trigger.dev/* packages to v4.4.3 using your package manager:

Self-hosted users: update your Docker image to ghcr.io/triggerdotdev/trigger.dev:v4.4.3.