@trigger.dev/[email protected]

Patch Changes

• Fixed the missing icons in trigger spans (#1506)
• Public access token scopes with just tags or just a batch can now access runs that have those tags or are in the batch. Previously, the only way to access a run was to have a specific scope for that exact run. (#1511)
• Updated dependencies:
  • @trigger.dev/[email protected]

@trigger.dev/[email protected]

Patch Changes

• Updated dependencies:
  • @trigger.dev/[email protected]

@trigger.dev/[email protected]

Patch Changes

• Public access token scopes with just tags or just a batch can now access runs that have those tags or are in the batch. Previously, the only way to access a run was to have a specific scope for that exact run. (#1511)
• Updated dependencies:
  • @trigger.dev/[email protected]

@trigger.dev/[email protected]

@trigger.dev/[email protected]

@trigger.dev/[email protected]

Patch Changes

• Updated dependencies:
  • @trigger.dev/[email protected]

@trigger.dev/[email protected]

What's Changed

• Batch Trigger upgrades by @ericallam in #1502
• Added new run filters and added some database indexes to speed them up
• Added a Batches page with filters
• Improved the text selection style by @samejr in #1497
• Update Infisical instructions to new SDK by @Fgc17 in #1493
• Deploy page table rows stay selected when the side menu is open by @samejr in #1492
• Always show alerts tab and lock email alerts when keys are missing by @ghostdevv in #1478
• Help panel by @samejr in #1488
• Adds Realtime concurrency limits to the billing page pricing tiers by @samejr in #1500

New Contributors

• @Fgc17 made their first contribution in #1493

Full Changelog: v.docker.3.2.2...v.docker.3.3.0

https://github.com/triggerdotdev/trigger.dev/pkgs/container/trigger.dev/313846744?tag=v3.3.0

[email protected]

Patch Changes

• 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",
      };
    },
  });

• Updated dependencies:

  • @trigger.dev/[email protected]
  • @trigger.dev/[email protected]

@trigger.dev/[email protected]

Minor Changes

• 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" });

  Breaking Changes

  • 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.

Patch Changes

• 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/[email protected]

@trigger.dev/[email protected]

Patch Changes

• Updated dependencies:
  • @trigger.dev/[email protected]

@trigger.dev/[email protected]

Minor Changes

• 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" });

  Breaking Changes

  • 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.

Patch Changes

• Added ability to subscribe to a batch of runs using runs.subscribeToBatch (#1502)
• Updated dependencies:
  • @trigger.dev/[email protected]