New package release: @v3.0.0-beta.15 - Trigger.dev | The open source background jobs framework

Today we're releasing packages v3.0.0-beta.15 with some breaking changes, fixes, and API improvements.

Breaking changes

v3.0.0-beta.15 updates the Task.trigger, Task.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);
}

Fixes

Fixes an issue when using idempotency keys with triggerAndWait and batchTriggerAndWait failing to resume if the idempotency key matched an already completed run.
Add additional logging around cleaning up dev workers, and always kill them after 5 seconds if they haven't already exited
Fixes an issue that caused failed tasks when resuming after calling triggerAndWait or batchTriggerAndWait in prod/staging (this doesn't effect dev).

The version of Node.js we use for deployed workers (latest 20) would crash with an out-of-memory error when the checkpoint was restored. This crash does not happen on Node 18x or Node21x, so we've decided to upgrade the worker version to Node.js21x, to mitigate this issue.

You'll need to re-deploy to production to fix the issue.

Improvements

We no longer limit individual task concurrency when no concurrency limit is set for the task or the queue the task belongs to. The concurrency limit will fall back to the org/env concurrency limit instead.

Upgrade now

To upgrade to v3.0.0-beta.15, run:

npm install @trigger-dev/[email protected]

yarn add @trigger-dev/[email protected]

pnpm add @trigger-dev/[email protected]