Add input streams for bidirectional communication with running tasks. Define typed input streams with streams.input<T>({ id }), then consume inside tasks via .wait() (suspends the process), .once() (waits for next message), or .on() (subscribes to a continuous stream). Send data from backends with .send(runId, data) or from frontends with the new useInputStreamSend React hook. (#3146)

Upgrade S2 SDK from 0.17 to 0.22 with support for custom endpoints (s2-lite) via the new endpoints configuration, AppendRecord.string() API, and maxInflightBytes session option.

fix(sdk): batch triggerAndWait variants now return correct run.taskIdentifier instead of unknown (#3080)

Add PAYLOAD_TOO_LARGE error to handle graceful recovery of sending batch trigger items with payloads that exceed the maximum payload size (#3137)

Updated dependencies:

• @trigger.dev/core@4.4.2

• @trigger.dev/core@4.4.1

Added query.execute() which lets you query your Trigger.dev data using TRQL (Trigger Query Language) and returns results as typed JSON rows or CSV. It supports configurable scope (environment, project, or organization), time filtering via period or from/to ranges, and a format option for JSON or CSV output. (#3060)

import { query } from "@trigger.dev/sdk";
import type { QueryTable } from "@trigger.dev/sdk";

// Basic untyped query
const result = await query.execute("SELECT run_id, status FROM runs LIMIT 10");

// Type-safe query using QueryTable to pick specific columns
const typedResult = await query.execute<QueryTable<"runs", "run_id" | "status" | "triggered_at">>(
  "SELECT run_id, status, triggered_at FROM runs LIMIT 10"
);
typedResult.results.forEach((row) => {
  console.log(row.run_id, row.status); // Fully typed
});

// Aggregation query with inline types
const stats = await query.execute<{ status: string; count: number }>(
  "SELECT status, COUNT(*) as count FROM runs GROUP BY status",
  { scope: "project", period: "30d" }
);

// CSV export
const csv = await query.execute("SELECT run_id, status FROM runs", {
  format: "csv",
  period: "7d",
});
console.log(csv.results); // Raw CSV string

Add maxDelay option to debounce feature. This allows setting a maximum time limit for how long a debounced run can be delayed, ensuring execution happens within a specified window even with continuous triggers. (#2984)

await myTask.trigger(payload, {
  debounce: {
    key: "my-key",
    delay: "5s",
    maxDelay: "30m", // Execute within 30 minutes regardless of continuous triggers
  },
});

Aligned the SDK's getRunIdForOptions logic with the Core package to handle semantic targets (root, parent) in root tasks. (#2874)

Export AnyOnStartAttemptHookFunction type to allow defining onStartAttempt hooks for individual tasks. (#2966)

Fixed a minor issue in the deployment command on distinguishing between local builds for the cloud vs local builds for self-hosting setups. (#3070)

Updated dependencies:

• @trigger.dev/core@4.4.0

Add support for AI SDK v6 (Vercel AI SDK) (#2919)

• Updated peer dependency to allow ai@^6.0.0 alongside v4 and v5
• Updated internal code to handle async validation from AI SDK v6's Schema type

Expose user-provided idempotency key and scope in task context. ctx.run.idempotencyKey now returns the original key passed to idempotencyKeys.create() instead of the hash, and ctx.run.idempotencyKeyScope shows the scope ("run", "attempt", or "global"). (#2903)

Updated dependencies:

• @trigger.dev/core@4.3.3

• @trigger.dev/core@4.3.2

• @trigger.dev/core@4.3.1

• @trigger.dev/core@4.3.0

• @trigger.dev/core@4.2.0

• @trigger.dev/core@4.1.2

• @trigger.dev/core@4.1.1

Realtime streams v2 (#2632)

Prevent uncaught errors in the onSuccess, onComplete, and onFailure lifecycle hooks from failing attempts/runs. (#2515)

Deprecated the onStart lifecycle hook (which only fires before the run function on the first attempt). Replaced with onStartAttempt that fires before the run function on every attempt:

export const taskWithOnStartAttempt = task({
  id: "task-with-on-start-attempt",
  onStartAttempt: async ({ payload, ctx }) => {
    //...
  },
  run: async (payload: any, { ctx }) => {
    //...
  },
});

// Default a global lifecycle hook using tasks
tasks.onStartAttempt(({ ctx, payload, task }) => {
  console.log(
    `Run ${ctx.run.id} started on task ${task} attempt ${ctx.run.attempt.number}`,
    ctx.run
  );
});

If you want to execute code before just the first attempt, you can use the onStartAttempt function and check ctx.run.attempt.number === 1:

export const taskWithOnStartAttempt = task({
  id: "task-with-on-start-attempt",
  onStartAttempt: async ({ payload, ctx }) => {
    if (ctx.run.attempt.number === 1) {
      console.log("Run started on attempt 1", ctx.run);
    }
  },
});

• @trigger.dev/core@4.1.0

• @trigger.dev/core@4.0.7

• @trigger.dev/core@4.0.6

• @trigger.dev/core@4.0.5

• @trigger.dev/core@4.0.4

• @trigger.dev/core@4.0.3

• @trigger.dev/core@4.0.2

• @trigger.dev/core@4.0.1

fix: importing from runEngine/index.js breaks non-node runtimes (#2328)

Run Engine 2.0 (alpha) (#1575)

fix: Logging large objects is now much more performant and uses less memory (#2263)

New internal idempotency implementation for trigger and batch trigger to prevent request retries from duplicating work (#2256)

When you create a Waitpoint token using wait.createToken() you get a URL back that can be used to complete it by making an HTTP POST request. (#2025)

feat: Support AI SDK 5.0. ai.tool now accepts either a schemaTask or a task with a provided jsonSchema (#2396)

External Trace Correlation & OpenTelemetry Package Updates. (#2334)

We will now correlate your external traces with trigger.dev traces and logs when using our external exporters:

import { defineConfig } from "@trigger.dev/sdk";
import { OTLPLogExporter } from "@opentelemetry/exporter-logs-otlp-http";
import { OTLPTraceExporter } from "@opentelemetry/exporter-trace-otlp-http";

export default defineConfig({
  project: process.env.TRIGGER_PROJECT_REF,
  dirs: ["./src/trigger"],
  telemetry: {
    logExporters: [
      new OTLPLogExporter({
        url: "https://api.axiom.co/v1/logs",
        headers: {
          Authorization: `Bearer ${process.env.AXIOM_TOKEN}`,
          "X-Axiom-Dataset": "test",
        },
      }),
    ],
    exporters: [
      new OTLPTraceExporter({
        url: "https://api.axiom.co/v1/traces",
        headers: {
          Authorization: `Bearer ${process.env.AXIOM_TOKEN}`,
          "X-Axiom-Dataset": "test",
        },
      }),
    ],
  },
  maxDuration: 3600,
});

You can also now propagate your external trace context when calling back into your own backend infra from inside a trigger.dev task:

import { otel, task } from "@trigger.dev/sdk";
import { context, propagation } from "@opentelemetry/api";

async function callNextjsApp() {
  return await otel.withExternalTrace(async () => {
    const headersObject = {};

    // Now context.active() refers to your external trace context
    propagation.inject(context.active(), headersObject);

    const result = await fetch("http://localhost:3000/api/demo-call-from-trigger", {
      headers: new Headers(headersObject),
      method: "POST",
      body: JSON.stringify({
        message: "Hello from Trigger.dev",
      }),
    });

    return result.json();
  });
}

export const myTask = task({
  id: "my-task",
  run: async (payload: any) => {
    await callNextjsApp();
  },
});

Add jsonSchema support when indexing tasks (#2353)

Fixed an issue with realtime streams that timeout and resume streaming dropping chunks (#1993)

Added and cleaned up the run ctx param: (#2322)

• New optional properties ctx.run.parentTaskRunId and ctx.run.rootTaskRunId reference the current run's root/parent ID.
• Removed deprecated properties from ctx
• Added a new ctx.deployment object that contains information about the deployment associated with the run.

We also update metadata.root and metadata.parent to work even when the run is a "root" run (meaning it doesn't have a parent or a root associated run). This now works:

metadata.root.set("foo", "bar");
metadata.parent.set("baz", 1);
metadata.current().foo; // "bar"
metadata.current().baz; // 1

The envvars.list() and retrieve() functions receive isSecret for each value. Secret values are always redacted. (#1942)

Fix issue where realtime streams would cut off after 5 minutes (#1952)

Deprecate toolTask and replace with ai.tool(mySchemaTask) (#1863)

Display clickable links in Cursor terminal (#1998)

Removes the releaseConcurrencyOnWaitpoint option on queues and the releaseConcurrency option on various wait functions. Replaced with the following default behavior: (#2284)

• Concurrency is never released when a run is first blocked via a waitpoint, at either the env or queue level.
• Concurrency is always released when a run is checkpointed and shutdown, at both the env and queue level.

Additionally, environment concurrency limits now have a new "Burst Factor", defaulting to 2.0x. The "Burst Factor" allows the environment-wide concurrency limit to be higher than any individual queue's concurrency limit. For example, if you have an environment concurrency limit of 100, and a Burst Factor of 2.0x, then you can execute up to 200 runs concurrently, but any one task/queue can still only execute 100 runs concurrently.

We've done some work cleaning up the run statuses. The new statuses are:

• PENDING_VERSION: Task is waiting for a version update because it cannot execute without additional information (task, queue, etc.)
• QUEUED: Task is waiting to be executed by a worker
• DEQUEUED: Task has been dequeued and is being sent to a worker to start executing.
• EXECUTING: Task is currently being executed by a worker
• WAITING: Task has been paused by the system, and will be resumed by the system
• COMPLETED: Task has been completed successfully
• CANCELED: Task has been canceled by the user
• FAILED: Task has failed to complete, due to an error in the system
• CRASHED: Task has crashed and won't be retried, most likely the worker ran out of resources, e.g. memory or storage
• SYSTEM_FAILURE: Task has failed to complete, due to an error in the system
• DELAYED: Task has been scheduled to run at a specific time
• EXPIRED: Task has expired and won't be executed
• TIMED_OUT: Task has reached it's maxDuration and has been stopped

We've removed the following statuses:

• WAITING_FOR_DEPLOY: This is no longer used, and is replaced by PENDING_VERSION
• FROZEN: This is no longer used, and is replaced by WAITING
• INTERRUPTED: This is no longer used
• REATTEMPTING: This is no longer used, and is replaced by EXECUTING

We've also added "boolean" helpers to runs returned via the API and from Realtime:

• isQueued: Returns true when the status is QUEUED, PENDING_VERSION, or DELAYED
• isExecuting: Returns true when the status is EXECUTING, DEQUEUED. These count against your concurrency limits.
• isWaiting: Returns true when the status is WAITING. These do not count against your concurrency limits.
• isCompleted: Returns true when the status is any of the completed statuses.
• isCanceled: Returns true when the status is CANCELED
• isFailed: Returns true when the status is any of the failed statuses.
• isSuccess: Returns true when the status is COMPLETED

This change adds the ability to easily detect which runs are being counted against your concurrency limit by filtering for both EXECUTING or DEQUEUED.

Add onCancel lifecycle hook (#2022)

Provide realtime skipColumns option via untamperable public access tokens (#2201)

Removed triggerAndPoll. It was never recommended so it's been removed. (#2379)

Improve metadata flushing efficiency by collapsing operations (#2106)

Upgrade to zod 3.25.76 (#2352)

Specify a region override when triggering a run (#2366)

Added runs.list filtering for queue and machine (#2277)

maintain proper context in metadata.root and parent getters (#1917)

v4: New lifecycle hooks (#1817)

Updated dependencies:

• @trigger.dev/core@4.0.0

• @trigger.dev/core@4.0.0-v4-beta.28

External Trace Correlation & OpenTelemetry Package Updates. (#2334)

We will now correlate your external traces with trigger.dev traces and logs when using our external exporters:

import { defineConfig } from "@trigger.dev/sdk";
import { OTLPLogExporter } from "@opentelemetry/exporter-logs-otlp-http";
import { OTLPTraceExporter } from "@opentelemetry/exporter-trace-otlp-http";

export default defineConfig({
  project: process.env.TRIGGER_PROJECT_REF,
  dirs: ["./src/trigger"],
  telemetry: {
    logExporters: [
      new OTLPLogExporter({
        url: "https://api.axiom.co/v1/logs",
        headers: {
          Authorization: `Bearer ${process.env.AXIOM_TOKEN}`,
          "X-Axiom-Dataset": "test",
        },
      }),
    ],
    exporters: [
      new OTLPTraceExporter({
        url: "https://api.axiom.co/v1/traces",
        headers: {
          Authorization: `Bearer ${process.env.AXIOM_TOKEN}`,
          "X-Axiom-Dataset": "test",
        },
      }),
    ],
  },
  maxDuration: 3600,
});

You can also now propagate your external trace context when calling back into your own backend infra from inside a trigger.dev task:

import { otel, task } from "@trigger.dev/sdk";
import { context, propagation } from "@opentelemetry/api";

async function callNextjsApp() {
  return await otel.withExternalTrace(async () => {
    const headersObject = {};

    // Now context.active() refers to your external trace context
    propagation.inject(context.active(), headersObject);

    const result = await fetch("http://localhost:3000/api/demo-call-from-trigger", {
      headers: new Headers(headersObject),
      method: "POST",
      body: JSON.stringify({
        message: "Hello from Trigger.dev",
      }),
    });

    return result.json();
  });
}

export const myTask = task({
  id: "my-task",
  run: async (payload: any) => {
    await callNextjsApp();
  },
});

Add jsonSchema support when indexing tasks (#2353)

Removed triggerAndPoll. It was never recommended so it's been removed. (#2379)

Upgrade to zod 3.25.76 (#2352)

Specify a region override when triggering a run (#2366)

Updated dependencies:

• @trigger.dev/core@4.0.0-v4-beta.27

fix: importing from runEngine/index.js breaks non-node runtimes (#2328)

Added and cleaned up the run ctx param: (#2322)

• New optional properties ctx.run.parentTaskRunId and ctx.run.rootTaskRunId reference the current run's root/parent ID.
• Removed deprecated properties from ctx
• Added a new ctx.deployment object that contains information about the deployment associated with the run.

We also update metadata.root and metadata.parent to work even when the run is a "root" run (meaning it doesn't have a parent or a root associated run). This now works:

metadata.root.set("foo", "bar");
metadata.parent.set("baz", 1);
metadata.current().foo; // "bar"
metadata.current().baz; // 1

Updated dependencies:

• @trigger.dev/core@4.0.0-v4-beta.26

• @trigger.dev/core@4.0.0-v4-beta.25

Removes the releaseConcurrencyOnWaitpoint option on queues and the releaseConcurrency option on various wait functions. Replaced with the following default behavior: (#2284)

• Concurrency is never released when a run is first blocked via a waitpoint, at either the env or queue level.
• Concurrency is always released when a run is checkpointed and shutdown, at both the env and queue level.

Additionally, environment concurrency limits now have a new "Burst Factor", defaulting to 2.0x. The "Burst Factor" allows the environment-wide concurrency limit to be higher than any individual queue's concurrency limit. For example, if you have an environment concurrency limit of 100, and a Burst Factor of 2.0x, then you can execute up to 200 runs concurrently, but any one task/queue can still only execute 100 runs concurrently.

We've done some work cleaning up the run statuses. The new statuses are:

• PENDING_VERSION: Task is waiting for a version update because it cannot execute without additional information (task, queue, etc.)
• QUEUED: Task is waiting to be executed by a worker
• DEQUEUED: Task has been dequeued and is being sent to a worker to start executing.
• EXECUTING: Task is currently being executed by a worker
• WAITING: Task has been paused by the system, and will be resumed by the system
• COMPLETED: Task has been completed successfully
• CANCELED: Task has been canceled by the user
• FAILED: Task has failed to complete, due to an error in the system
• CRASHED: Task has crashed and won't be retried, most likely the worker ran out of resources, e.g. memory or storage
• SYSTEM_FAILURE: Task has failed to complete, due to an error in the system
• DELAYED: Task has been scheduled to run at a specific time
• EXPIRED: Task has expired and won't be executed
• TIMED_OUT: Task has reached it's maxDuration and has been stopped

We've removed the following statuses:

• WAITING_FOR_DEPLOY: This is no longer used, and is replaced by PENDING_VERSION
• FROZEN: This is no longer used, and is replaced by WAITING
• INTERRUPTED: This is no longer used
• REATTEMPTING: This is no longer used, and is replaced by EXECUTING

We've also added "boolean" helpers to runs returned via the API and from Realtime:

• isQueued: Returns true when the status is QUEUED, PENDING_VERSION, or DELAYED
• isExecuting: Returns true when the status is EXECUTING, DEQUEUED. These count against your concurrency limits.
• isWaiting: Returns true when the status is WAITING. These do not count against your concurrency limits.
• isCompleted: Returns true when the status is any of the completed statuses.
• isCanceled: Returns true when the status is CANCELED
• isFailed: Returns true when the status is any of the failed statuses.
• isSuccess: Returns true when the status is COMPLETED

This change adds the ability to easily detect which runs are being counted against your concurrency limit by filtering for both EXECUTING or DEQUEUED.

Added runs.list filtering for queue and machine (#2277)

Updated dependencies:

• @trigger.dev/core@4.0.0-v4-beta.24

• @trigger.dev/core@4.0.0-v4-beta.23

• @trigger.dev/core@4.0.0-v4-beta.22

• @trigger.dev/core@4.0.0-v4-beta.21

• @trigger.dev/core@4.0.0-v4-beta.20

• @trigger.dev/core@4.0.0-v4-beta.19

• @trigger.dev/core@4.0.0-v4-beta.18

• @trigger.dev/core@4.0.0-v4-beta.17

• @trigger.dev/core@4.0.0-v4-beta.16

• @trigger.dev/core@4.0.0-v4-beta.15

• @trigger.dev/core@4.0.0-v4-beta.14

• @trigger.dev/core@4.0.0-v4-beta.13

• @trigger.dev/core@4.0.0-v4-beta.12

• @trigger.dev/core@4.0.0-v4-beta.11

• @trigger.dev/core@4.0.0-v4-beta.10

• @trigger.dev/core@4.0.0-v4-beta.9

• @trigger.dev/core@4.0.0-v4-beta.8

• @trigger.dev/core@4.0.0-v4-beta.7

• @trigger.dev/core@4.0.0-v4-beta.6

• @trigger.dev/core@4.0.0-v4-beta.5

• @trigger.dev/core@4.0.0-v4-beta.4

• @trigger.dev/core@4.0.0-v4-beta.3

• @trigger.dev/core@4.0.0-v4-beta.2

• @trigger.dev/core@4.0.0-v4-beta.1

• @trigger.dev/core@4.0.0-v4-beta.0

• @trigger.dev/core@3.3.17

You can add Alerts in the dashboard. One of these is a webhook, which this change greatly improves. (#1703)

The main change is that there's now an SDK function to verify and parse them (similar to Stripe SDK).

const event = await webhooks.constructEvent(request, process.env.ALERT_WEBHOOK_SECRET!);

If the signature you provide matches the one from the dashboard when you create the webhook, you will get a nicely typed object back for these three types:

• "alert.run.failed"
• "alert.deployment.success"
• "alert.deployment.failed"

Updated dependencies:

• @trigger.dev/core@3.3.16

• @trigger.dev/core@3.3.15

• @trigger.dev/core@3.3.14

• @trigger.dev/core@3.3.13

• @trigger.dev/core@3.3.12

Add support for specifying machine preset at trigger time. Works with any trigger function: (#1608)

// Same as usual, will use the machine preset on childTask, defaults to "small-1x"
await childTask.trigger({ message: "Hello, world!" });

// This will override the task's machine preset and any defaults. Works with all trigger functions.
await childTask.trigger({ message: "Hello, world!" }, { machine: "small-2x" });
await childTask.triggerAndWait({ message: "Hello, world!" }, { machine: "small-2x" });

await childTask.batchTrigger([
  { payload: { message: "Hello, world!" }, options: { machine: "micro" } },
  { payload: { message: "Hello, world!" }, options: { machine: "large-1x" } },
]);
await childTask.batchTriggerAndWait([
  { payload: { message: "Hello, world!" }, options: { machine: "micro" } },
  { payload: { message: "Hello, world!" }, options: { machine: "large-1x" } },
]);

await tasks.trigger<typeof childTask>(
  "child",
  { message: "Hello, world!" },
  { machine: "small-2x" }
);
await tasks.batchTrigger<typeof childTask>("child", [
  { payload: { message: "Hello, world!" }, options: { machine: "micro" } },
  { payload: { message: "Hello, world!" }, options: { machine: "large-1x" } },
]);

Updated dependencies:

• @trigger.dev/core@3.3.11

• @trigger.dev/core@3.3.10

• @trigger.dev/core@3.3.9

• @trigger.dev/core@3.3.8

• Fixes an issue in streams where "chunks" could get split across multiple reads (#1549)
• Fixed stopping the run subscription after a run is finished, when using useRealtimeRun or useRealtimeRunWithStreams
• Added an onComplete callback to useRealtimeRun and useRealtimeRunWithStreams
• Optimized the run subscription to reduce unnecessary updates

• @trigger.dev/core@3.3.7

• @trigger.dev/core@3.3.6

• @trigger.dev/core@3.3.5

• @trigger.dev/core@3.3.4

• @trigger.dev/core@3.3.3

• @trigger.dev/core@3.3.2

• @trigger.dev/core@3.3.1

Improved Batch Triggering: (#1502)

• The new Batch Trigger endpoint is now asynchronous and supports up to 500 runs per request.

• The new endpoint also supports triggering multiple different tasks in a single batch request (support in the SDK coming soon).

• The existing batchTrigger method now supports the new endpoint, and shouldn't require any changes to your code.

• Idempotency keys now expire after 24 hours, and you can customize the expiration time when creating a new key by using the idempotencyKeyTTL parameter:

await myTask.batchTrigger([{ payload: { foo: "bar" } }], {
  idempotencyKey: "my-key",
  idempotencyKeyTTL: "60s",
});
// Works for individual items as well:
await myTask.batchTrigger([
  { payload: { foo: "bar" }, options: { idempotencyKey: "my-key", idempotencyKeyTTL: "60s" } },
]);
// And `trigger`:
await myTask.trigger({ foo: "bar" }, { idempotencyKey: "my-key", idempotencyKeyTTL: "60s" });

• We've removed the idempotencyKey option from triggerAndWait and batchTriggerAndWait, because it can lead to permanently frozen runs in deployed tasks. We're working on upgrading our entire system to support idempotency keys on these methods, and we'll re-add the option once that's complete.

Added new batch.trigger and batch.triggerByTask methods that allows triggering multiple different tasks in a single batch: (#1502)

import { batch } from "@trigger.dev/sdk/v3";
import type { myTask1, myTask2 } from "./trigger/tasks";

// Somewhere in your backend code
const response = await batch.trigger<typeof myTask1 | typeof myTask2>([
  { id: "task1", payload: { foo: "bar" } },
  { id: "task2", payload: { baz: "qux" } },
]);

for (const run of response.runs) {
  if (run.ok) {
    console.log(run.output);
  } else {
    console.error(run.error);
  }
}

Or if you are inside of a task, you can use triggerByTask:

import { batch, task, runs } from "@trigger.dev/sdk/v3";

export const myParentTask = task({
  id: "myParentTask",
  run: async () => {
    const response = await batch.triggerByTask([
      { task: myTask1, payload: { foo: "bar" } },
      { task: myTask2, payload: { baz: "qux" } },
    ]);

    const run1 = await runs.retrieve(response.runs[0]);
    console.log(run1.output); // typed as { foo: string }

    const run2 = await runs.retrieve(response.runs[1]);
    console.log(run2.output); // typed as { baz: string }

    const response2 = await batch.triggerByTaskAndWait([
      { task: myTask1, payload: { foo: "bar" } },
      { task: myTask2, payload: { baz: "qux" } },
    ]);

    if (response2.runs[0].ok) {
      console.log(response2.runs[0].output); // typed as { foo: string }
    }

    if (response2.runs[1].ok) {
      console.log(response2.runs[1].output); // typed as { baz: string }
    }
  },
});

export const myTask1 = task({
  id: "myTask1",
  run: async () => {
    return {
      foo: "bar",
    };
  },
});

export const myTask2 = task({
  id: "myTask2",
  run: async () => {
    return {
      baz: "qux",
    };
  },
});

Added ability to subscribe to a batch of runs using runs.subscribeToBatch (#1502)

Updated dependencies:

• @trigger.dev/core@3.3.0

• @trigger.dev/core@3.2.2

• @trigger.dev/core@3.2.1

• @trigger.dev/core@3.2.0

• @trigger.dev/core@3.1.2

• @trigger.dev/core@3.1.1

• @trigger.dev/core@3.1.0

• @trigger.dev/core@3.0.13

• @trigger.dev/core@3.0.12

• @trigger.dev/core@3.0.11

• @trigger.dev/core@3.0.10

• @trigger.dev/core@3.0.9

• @trigger.dev/core@3.0.8

• @trigger.dev/core@3.0.7

• @trigger.dev/core@3.0.6

• @trigger.dev/core@3.0.4

• @trigger.dev/core@3.0.3

• @trigger.dev/core@3.0.1

b66d5525e: add machine config and secure zod connection

9491a1649: Implement task.onSuccess/onFailure and config.onSuccess/onFailure

b271742dc: Configurable log levels in the config file and via env var

0591db5f2: Fixes for continuing after waits

f9ec66c56: New Build System

8cae1d087: Fix trigger functions for custom queues

3a1b0c486: v3: Environment variable management API and SDK, along with resolveEnvVars CLI hook

979bee50d: Fix return type of runs.retrieve, and allow passing the type of the task to runs.retrieve

b68012f81: Make msw a normal dependency (for now) to fix Module Not Found error in Next.js.

It turns out that webpack will "hoist" dynamically imported modules and attempt to resolve them at build time, even though it's an optional peer dep:

https://x.com/maverickdotdev/status/1782465214308319404

203e00208: Add runs.retrieve management API method to get info about a run by run ID

1b90ffbb8: v3: Usage tracking

51bb4c887: Fix for calling trigger and passing a custom queue

4986bfda2: Export queue from the SDK

086a0f95c: Extract common trigger code into internal functions and add a tasks.batchTriggerAndWait function

4f95c9de4: v3: recover from server rate limiting errors in a more reliable way

0591db5f2: Rollback to try and fix some dependent attempt issues

8578c9b28: Support self-hosters pushing to a custom registry when running deploy

0e77e7ef7: v3: Trigger delayed runs and reschedule them

ecf1110ab: v3: Export AbortTaskRunError from @trigger.dev/sdk/v3

f854cb90e: Added replayRun function to the SDK

44e1b8754: Improve the SDK function types and expose a new APIError instead of the APIResult type

55264657d: You can now add tags to runs and list runs using them

6d9dfbc75: Add configure function to be able to configure the SDK manually

ecef19966: Use global setTimeout to ensure cross-runtime support

719c0a0b9: Fixed incorrect span timings around checkpoints by implementing a precise wall clock that resets after restores

4986bfda2: Adding task with a triggerSource of schedule

e9a63a486: Lock SDK and CLI deps on exact core version

374edef02: Updates the trigger, batchTrigger and their *AndWait variants to use the first parameter for the payload/items, and the second parameter for options.

Before:

await yourTask.trigger({ payload: { foo: "bar" }, options: { idempotencyKey: "key_1234" } });
await yourTask.triggerAndWait({
  payload: { foo: "bar" },
  options: { idempotencyKey: "key_1234" },
});

await yourTask.batchTrigger({
  items: [{ payload: { foo: "bar" } }, { payload: { foo: "baz" } }],
});
await yourTask.batchTriggerAndWait({
  items: [{ payload: { foo: "bar" } }, { payload: { foo: "baz" } }],
});

After:

await yourTask.trigger({ foo: "bar" }, { idempotencyKey: "key_1234" });
await yourTask.triggerAndWait({ foo: "bar" }, { idempotencyKey: "key_1234" });

await yourTask.batchTrigger([{ payload: { foo: "bar" } }, { payload: { foo: "baz" } }]);
await yourTask.batchTriggerAndWait([{ payload: { foo: "bar" } }, { payload: { foo: "baz" } }]);

We've also changed the API of the triggerAndWait result. Before, if the subtask that was triggered finished with an error, we would automatically "rethrow" the error in the parent task.

Now instead we're returning a TaskRunResult object that allows you to discriminate between successful and failed runs in the subtask:

Before:

try {
  const result = await yourTask.triggerAndWait({ foo: "bar" });

  // result is the output of your task
  console.log("result", result);
} catch (error) {
  // handle subtask errors here
}

After:

const result = await yourTask.triggerAndWait({ foo: "bar" });

if (result.ok) {
  console.log(`Run ${result.id} succeeded with output`, result.output);
} else {
  console.log(`Run ${result.id} failed with error`, result.error);
}

26093896d: When using idempotency keys, triggerAndWait and batchTriggerAndWait will still work even if the existing runs have already been completed (or even partially completed, in the case of batchTriggerAndWait)

• TaskRunExecutionResult.id is now the run friendlyId, not the attempt friendlyId
• A single TaskRun can now have many batchItems, in the case of batchTriggerAndWait while using idempotency keys
• A run’s idempotencyKey is now added to the ctx as well as the TaskEvent and displayed in the span view
• When resolving batchTriggerAndWait, the runtimes no longer reject promises, leading to an error in the parent task

b68012f81: Move to our global system from AsyncLocalStorage for the current task context storage

c9e1a3e9c: Remove unimplemented batchOptions

cf13fbdf3: Add triggerAndWait().unwrap() to more easily get at the output or throw the subtask error

3f8b6d8fc: v2: Better handle recovering from platform communication errors by auto-yielding back to the platform in case of temporary API failures

1281d40e4: When a v2 run hits the rate limit, reschedule with the reset date

ba71f959e: Management SDK overhaul and adding the runs.list API

7c36a1a4b: v3: Adding SDK functions for triggering tasks in a typesafe way, without importing task file

f93eae300: Dynamically import superjson and fix some bundling issues

c405ae711: Added timezone support to schedules

34ca7667d: v3: Include presigned urls for downloading large payloads and outputs when using runs.retrieve

8ba998794: Added declarative cron schedules

f854cb90e: Added cancelRun to the SDK

4986bfda2: Added a new global - Task Catalog - to better handle task metadata

b68012f81: Extracting out all the non-SDK related features from the main @trigger.dev/core/v3 export

8578c9b28: Remove msw and retry.interceptFetch

Updated dependencies [ed2a26c86]

Updated dependencies [c702d6a9c]

Updated dependencies [9882d66f8]

Updated dependencies [b66d5525e]

Updated dependencies [e3db25739]

Updated dependencies [9491a1649]

Updated dependencies [1670c4c41]

Updated dependencies [b271742dc]

Updated dependencies [cf13fbdf3]

Updated dependencies [dbda820a7]

Updated dependencies [4986bfda2]

Updated dependencies [eb6012628]

Updated dependencies [f9ec66c56]

Updated dependencies [f7d32b83b]

Updated dependencies [09413a62a]

Updated dependencies [3a1b0c486]

Updated dependencies [203e00208]

Updated dependencies [b4f9b70ae]

Updated dependencies [1b90ffbb8]

Updated dependencies [5cf90da72]

Updated dependencies [9af2570da]

Updated dependencies [7ea8532cc]

Updated dependencies [1477a2e30]

Updated dependencies [4f95c9de4]

Updated dependencies [83dc87155]

Updated dependencies [d490bc5cb]

Updated dependencies [e3cf456c6]

Updated dependencies [14c2bdf89]

Updated dependencies [9491a1649]

Updated dependencies [0ed93a748]

Updated dependencies [8578c9b28]

Updated dependencies [0e77e7ef7]

Updated dependencies [e417aca87]

Updated dependencies [568da0178]

Updated dependencies [c738ef39c]

Updated dependencies [ece6ca678]

Updated dependencies [f854cb90e]

Updated dependencies [0e919f56f]

Updated dependencies [44e1b8754]

Updated dependencies [55264657d]

Updated dependencies [6d9dfbc75]

Updated dependencies [e337b2165]

Updated dependencies [719c0a0b9]

Updated dependencies [4986bfda2]

Updated dependencies [e30beb779]

Updated dependencies [68d32429b]

Updated dependencies [374edef02]

Updated dependencies [e04d44866]

Updated dependencies [26093896d]

Updated dependencies [55d1f8c67]

Updated dependencies [c405ae711]

Updated dependencies [9e5382951]

Updated dependencies [b68012f81]

Updated dependencies [098932ea9]

Updated dependencies [68d32429b]

Updated dependencies [9835f4ec5]

Updated dependencies [3f8b6d8fc]

Updated dependencies [fde939a30]

Updated dependencies [1281d40e4]

Updated dependencies [ba71f959e]

Updated dependencies [395abe1b9]

Updated dependencies [03b104a3d]

Updated dependencies [f93eae300]

Updated dependencies [5ae3da6b4]

Updated dependencies [c405ae711]

Updated dependencies [34ca7667d]

Updated dependencies [8ba998794]

Updated dependencies [62c9a5b71]

Updated dependencies [392453e8a]

Updated dependencies [8578c9b28]

Updated dependencies [6a379e4e9]

Updated dependencies [f854cb90e]

Updated dependencies [584c7da5d]

Updated dependencies [4986bfda2]

Updated dependencies [e69ffd314]

Updated dependencies [b68012f81]

Updated dependencies [39885a427]

Updated dependencies [8578c9b28]

Updated dependencies [e69ffd314]

Updated dependencies [8578c9b28]

Updated dependencies [f04041744]

Updated dependencies [d934feb02]

• @trigger.dev/core@3.0.0

• @trigger.dev/core@3.0.0-beta.55
• @trigger.dev/core-backend@3.0.0-beta.55

• @trigger.dev/core@3.0.0-beta.54
• @trigger.dev/core-backend@3.0.0-beta.54

• @trigger.dev/core@3.0.0-beta.53
• @trigger.dev/core-backend@3.0.0-beta.53

• @trigger.dev/core@3.0.0-beta.52
• @trigger.dev/core-backend@3.0.0-beta.52

• @trigger.dev/core@3.0.0-beta.51
• @trigger.dev/core-backend@3.0.0-beta.51

• @trigger.dev/core@3.0.0-beta.50
• @trigger.dev/core-backend@3.0.0-beta.50

• @trigger.dev/core@3.0.0-beta.49
• @trigger.dev/core-backend@3.0.0-beta.49

• @trigger.dev/core@3.0.0-beta.48
• @trigger.dev/core-backend@3.0.0-beta.48

• @trigger.dev/core@3.0.0-beta.47
• @trigger.dev/core-backend@3.0.0-beta.47

• @trigger.dev/core@3.0.0-beta.46
• @trigger.dev/core-backend@3.0.0-beta.46

• @trigger.dev/core@3.0.0-beta.45
• @trigger.dev/core-backend@3.0.0-beta.45

• @trigger.dev/core@3.0.0-beta.44
• @trigger.dev/core-backend@3.0.0-beta.44

• @trigger.dev/core@3.0.0-beta.43
• @trigger.dev/core-backend@3.0.0-beta.43

• @trigger.dev/core@3.0.0-beta.42
• @trigger.dev/core-backend@3.0.0-beta.42

• @trigger.dev/core@3.0.0-beta.41
• @trigger.dev/core-backend@3.0.0-beta.41

• @trigger.dev/core@3.0.0-beta.40
• @trigger.dev/core-backend@3.0.0-beta.40

• @trigger.dev/core@3.0.0-beta.38
• @trigger.dev/core-backend@3.0.0-beta.38

• @trigger.dev/core@3.0.0-beta.37
• @trigger.dev/core-backend@3.0.0-beta.37

• @trigger.dev/core@3.0.0-beta.36
• @trigger.dev/core-backend@3.0.0-beta.36

• @trigger.dev/core@3.0.0-beta.35
• @trigger.dev/core-backend@3.0.0-beta.35

• @trigger.dev/core@3.0.0-beta.34
• @trigger.dev/core-backend@3.0.0-beta.34

• @trigger.dev/core@3.0.0-beta.33
• @trigger.dev/core-backend@3.0.0-beta.33

• @trigger.dev/core@3.0.0-beta.30
• @trigger.dev/core-backend@3.0.0-beta.30

• @trigger.dev/core@3.0.0-beta.28
• @trigger.dev/core-backend@3.0.0-beta.28

• @trigger.dev/core@3.0.0-beta.27
• @trigger.dev/core-backend@3.0.0-beta.27

• @trigger.dev/core@3.0.0-beta.25
• @trigger.dev/core-backend@3.0.0-beta.25

• @trigger.dev/core@3.0.0-beta.24
• @trigger.dev/core-backend@3.0.0-beta.24

• @trigger.dev/core@3.0.0-beta.21
• @trigger.dev/core-backend@3.0.0-beta.21

• @trigger.dev/core@3.0.0-beta.20
• @trigger.dev/core-backend@3.0.0-beta.20

• @trigger.dev/core@3.0.0-beta.19
• @trigger.dev/core-backend@3.0.0-beta.19

b68012f81: Make msw a normal dependency (for now) to fix Module Not Found error in Next.js.

It turns out that webpack will "hoist" dynamically imported modules and attempt to resolve them at build time, even though it's an optional peer dep:

https://x.com/maverickdotdev/status/1782465214308319404

b68012f81: Move to our global system from AsyncLocalStorage for the current task context storage

b68012f81: Extracting out all the non-SDK related features from the main @trigger.dev/core/v3 export

Updated dependencies [b68012f81]

Updated dependencies [b68012f81]

• @trigger.dev/core@3.0.0-beta.18
• @trigger.dev/core-backend@3.0.0-beta.18

• @trigger.dev/core@3.0.0-beta.16
• @trigger.dev/core-backend@3.0.0-beta.16

374edef02: Updates the trigger, batchTrigger and their *AndWait variants to use the first parameter for the payload/items, and the second parameter for options.

Before:

await yourTask.trigger({ payload: { foo: "bar" }, options: { idempotencyKey: "key_1234" } });
await yourTask.triggerAndWait({
  payload: { foo: "bar" },
  options: { idempotencyKey: "key_1234" },
});

await yourTask.batchTrigger({
  items: [{ payload: { foo: "bar" } }, { payload: { foo: "baz" } }],
});
await yourTask.batchTriggerAndWait({
  items: [{ payload: { foo: "bar" } }, { payload: { foo: "baz" } }],
});

After:

await yourTask.trigger({ foo: "bar" }, { idempotencyKey: "key_1234" });
await yourTask.triggerAndWait({ foo: "bar" }, { idempotencyKey: "key_1234" });

await yourTask.batchTrigger([{ payload: { foo: "bar" } }, { payload: { foo: "baz" } }]);
await yourTask.batchTriggerAndWait([{ payload: { foo: "bar" } }, { payload: { foo: "baz" } }]);

We've also changed the API of the triggerAndWait result. Before, if the subtask that was triggered finished with an error, we would automatically "rethrow" the error in the parent task.

Now instead we're returning a TaskRunResult object that allows you to discriminate between successful and failed runs in the subtask:

Before:

try {
  const result = await yourTask.triggerAndWait({ foo: "bar" });

  // result is the output of your task
  console.log("result", result);
} catch (error) {
  // handle subtask errors here
}

After:

const result = await yourTask.triggerAndWait({ foo: "bar" });

if (result.ok) {
  console.log(`Run ${result.id} succeeded with output`, result.output);
} else {
  console.log(`Run ${result.id} failed with error`, result.error);
}

26093896d: When using idempotency keys, triggerAndWait and batchTriggerAndWait will still work even if the existing runs have already been completed (or even partially completed, in the case of batchTriggerAndWait)

• TaskRunExecutionResult.id is now the run friendlyId, not the attempt friendlyId
• A single TaskRun can now have many batchItems, in the case of batchTriggerAndWait while using idempotency keys
• A run’s idempotencyKey is now added to the ctx as well as the TaskEvent and displayed in the span view
• When resolving batchTriggerAndWait, the runtimes no longer reject promises, leading to an error in the parent task

Updated dependencies [374edef02]

Updated dependencies [26093896d]

Updated dependencies [62c9a5b71]

• @trigger.dev/core@3.0.0-beta.15
• @trigger.dev/core-backend@3.0.0-beta.15

• @trigger.dev/core@3.0.0-beta.14
• @trigger.dev/core-backend@3.0.0-beta.14

• @trigger.dev/core@3.0.0-beta.13
• @trigger.dev/core-backend@3.0.0-beta.13

• @trigger.dev/core@3.0.0-beta.7
• @trigger.dev/core-backend@3.0.0-beta.7

• @trigger.dev/core@3.0.0-beta.6
• @trigger.dev/core-backend@3.0.0-beta.6

• @trigger.dev/core@3.0.0-beta.5
• @trigger.dev/core-backend@3.0.0-beta.5

• @trigger.dev/core@3.0.0-beta.3
• @trigger.dev/core-backend@3.0.0-beta.3

• @trigger.dev/core@3.0.0-beta.2
• @trigger.dev/core-backend@3.0.0-beta.2

• @trigger.dev/core@3.0.0-beta.1
• @trigger.dev/core-backend@3.0.0-beta.1

• @trigger.dev/core@3.0.0-beta.0
• @trigger.dev/core-backend@3.0.0-beta.0

• @trigger.dev/core@2.3.17
• @trigger.dev/core-backend@2.3.17

• @trigger.dev/core@2.3.16
• @trigger.dev/core-backend@2.3.16

• @trigger.dev/core@2.3.15
• @trigger.dev/core-backend@2.3.15

• @trigger.dev/core@2.3.13
• @trigger.dev/core-backend@2.3.13

• @trigger.dev/core@2.3.12
• @trigger.dev/core-backend@2.3.12

• @trigger.dev/core@2.3.10
• @trigger.dev/core-backend@2.3.10

• @trigger.dev/core@2.3.9
• @trigger.dev/core-backend@2.3.9

• @trigger.dev/core@2.3.4
• @trigger.dev/core-backend@2.3.4

• @trigger.dev/core-backend@2.3.1
• @trigger.dev/core@2.3.1

17f6f29d: Support for Deno, Bun and Cloudflare workers, as well as conditionally exporting ESM versions of the package instead of just commonjs.

Cloudflare worker support requires the node compat flag turned on (https://developers.cloudflare.com/workers/runtime-apis/nodejs/)

• @trigger.dev/core-backend@2.3.0
• @trigger.dev/core@2.3.0

• @trigger.dev/core@2.2.11
• @trigger.dev/core-backend@2.2.11

• @trigger.dev/core@2.2.9
• @trigger.dev/core-backend@2.2.9

• Add a Key-Value Store for use in and outside of Jobs
• Add a @trigger.dev/shopify package

• @trigger.dev/core@2.2.8
• @trigger.dev/core-backend@2.2.8

• @trigger.dev/core@2.2.7
• @trigger.dev/core-backend@2.2.7

• @trigger.dev/core@2.2.6
• @trigger.dev/core-backend@2.2.6

• @trigger.dev/core@2.2.5
• @trigger.dev/core-backend@2.2.5

• @trigger.dev/core-backend@2.2.4
• @trigger.dev/core@2.2.4

• @trigger.dev/core@2.2.3

• @trigger.dev/core@2.2.1

• @trigger.dev/core@2.2.0

• @trigger.dev/core@2.1.9

• @trigger.dev/core@2.1.8

• @trigger.dev/core@2.1.4

• @trigger.dev/core@2.1.3

• @trigger.dev/core@2.1.2

• @trigger.dev/core@2.1.1

• @trigger.dev/core@2.1.0

• @trigger.dev/core@2.1.0-beta.1

• @trigger.dev/core@2.1.0-beta.0

• @trigger.dev/core@2.0.14

• @trigger.dev/core@2.0.13

• @trigger.dev/core@2.0.11

• @trigger.dev/core@2.0.10

• @trigger.dev/core@2.0.9

• @trigger.dev/core@2.0.7

• @trigger.dev/core@2.0.6

• @trigger.dev/core@2.0.4

• @trigger.dev/core@2.0.2

• @trigger.dev/core@0.0.5