Trigger.dev 4.6.3 error cause chains: log the Sume code and request id

When a Trigger.dev task calls Sume and the call fails, throw a new error whose cause is the Sume error, with the error.code and request_id on it, because Trigger.dev v4.6.3 (2026-09-17) now captures thrown error cause chains and surfaces them in the dashboard, the CLI and alerts. The alert then names the Sume code that decided whether to retry, and the request id Sume support needs.

The Trigger.dev detail is from its changelog, read 2026-10-03, which gives only that one line about cause chains; Sume's envelope and codes are from Errors and rate limits and Generation admission. I did not run a task against v4.6.3.

What does a Sume error carry?

Public errors are a JSON envelope with error.code, error.message, error.request_id and details, and the request id is also in the response headers. Put code and request id into the cause's message or fields. Do not put the API key, signed URLs or raw media URLs there: Sume's docs say to leave those out of anything you share when reporting an issue.

Which codes should the task retry?

Decide before you throw. Fix-the-request codes should fail the run at once; capacity codes are retried with the same Idempotency-Key, so the retry returns the original job instead of billing twice. 429 queue_full means wait for jobs to finish or cancel queued ones; 429 rate_limited means back off with retry-after.