docs(limits): document automatic payload offloading for triggers and batches#4217
Conversation
|
WalkthroughUpdated the limits documentation to explain automatic offloading of large payloads and outputs, SDK pre-upload behavior for payloads over 128KB, applicable SDK versions, and presigned download URLs for retrieved data over 512KB. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
8d000ac to
9cbb9d0
Compare
9cbb9d0 to
7e51e3a
Compare
…batches Clarify that large payloads and outputs are offloaded to object storage transparently. Split the behaviour into the send path (SDK uploads any trigger or batch-item payload over 128KB before sending, single trigger since 4.5.0 and batch since 4.5.2) and the retrieve path (payloads/outputs over 512KB returned as a presigned URL from runs.retrieve).
7e51e3a to
58844be
Compare
@trigger.dev/build
trigger.dev
@trigger.dev/core
@trigger.dev/python
@trigger.dev/react-hooks
@trigger.dev/redis-worker
@trigger.dev/rsc
@trigger.dev/schema-to-json
@trigger.dev/sdk
commit: |
Summary
The limits page didn't spell out that large payloads offload to object storage automatically, and its single "512KB" note conflated two different thresholds. This clarifies the behaviour.
On the way in, the SDK uploads any trigger or batch-item payload over 128KB to object storage before sending, so large triggers and batches don't hit the request body limit (
trigger/triggerAndWaitsince 4.5.0,batchTrigger/batchTriggerAndWaitsince 4.5.2). On retrieval, payloads and outputs over 512KB are stored in object storage and returned as a presigned URL fromruns.retrieve.