Request and response
How the body becomes data, and how the reply is shaped and cached. Also the deadline and the per-channel trace policy.
| Page | Holds |
|---|---|
request | the auto and payload body modes, what each does to data and metadata, and the cookies a workflow may read. |
response | shaped status, headers, body and cookies from the workflow, and per-status error bodies for guard rejections. |
cache | serving repeated identical sync requests from a stored response, the cache key, key_logic, TTL and the backing store. |
timeout_ms | the workflow execution deadline, and how each ingress defaults or clamps it to a transport ceiling. |
tracing | a per-channel override of the trace persistence mode, sample rate and errors-only policy, plus task details. |
Related
- Channel configuration: every key, with its page.
- Guards by ingress: which guard runs where, and in what order.
- Configure a channel: the same keys, as a walkthrough.
Last verified 14 September 2026