bug: Task Output Offloading Fails Due to Undocumented "packets" Bucket Requirement

[zvictor]

Provide environment information

  System:
    OS: Linux 6.6 cpe:/o:nixos:nixos:24.11 24.11 (Vicuna)
    CPU: (8) x64 Intel(R) Core(TM) i7-4702MQ CPU @ 2.20GHz
    Memory: 3.60 GB / 15.54 GB
    Container: Yes
    Shell: 5.9 - /run/current-system/sw/bin/zsh
  Binaries:
    Node: 22.13.1 - /nix/store/l9vrjjavsgf5b5ypp5m9qcqnivsjpgbf-nodejs-22.13.1/bin/node
    npm: 10.9.2 - /nix/store/l9vrjjavsgf5b5ypp5m9qcqnivsjpgbf-nodejs-22.13.1/bin/npm
    pnpm: 10.3.0 - /nix/store/wma2if50cv4l2rlv5iskwhy7svc5wyrr-corepack-nodejs-22.13.1/bin/pnpm

Describe the bug

When hitting a task payload/output limit, Trigger tries to offload to the configured object storage. However, it expects a bucket called packets to exist, even though there is no documentation of it anywhere other than /apps/webapp/app/v3/r2.server.ts#L44.

Message: store.uploadOutput

TASK_OUTPUT_ERROR: 404 <?xml version="1.0" encoding="UTF-8"?><Error><Code>NoSuchBucket</Code><Message>The specified bucket does not exist.</Message></Error>

Reproduction repo

https://trigger.dev/docs/triggering#large-payloads

To reproduce

1. Deploy Trigger as self-hosting.
2. Add the S3 env vars.
3. Make sure your S3/R2 has no packets bucket created yet.
4. Run into a task payload/output limit.

You should see a NoSuchBucket error.

Additional information

Once the packets bucket is created, everything works fine.

[matt-aitken]

Hi @zvictor,

I'm assuming you're self-hosting?

There are docs on large payload/output support in our self-hosting docs here: https://trigger.dev/docs/open-source-self-hosting#large-payloads

Thanks

[zvictor]

Yes, I am self-hosting and I have setup the S3 access.

I just updated the To reproduce section to make the context of the issue more clear.