The Letterbox stores delivery results.
This is where you read what came back. A Letterflow occupies one retained entry, with its captured content kept in the selected execution regions.
Open a delivery
Result thumbnails show OK for clean completion, WARN for completion with ignored errors, ERR for a stopped or failed run, and CNCL for cancellation. A false Condition is successful. Warnings include On error: Continue and unchecked Letter error categories; a later failure still shows ERR.
The actual HTTP version
HTTP Version Used shows the negotiated version of the final response, after redirects and retries. It can differ from the Delivery Policy's preference. The field is absent for file transfers, missing responses, and older results without this metadata.
Request and response details
Read captured URLs, headers, bodies, host IP, and execution timestamps. Text is rendered safely; binary content is distinguished from text. Use full artifact downloads when a preview is not enough.
Search by result name and filter by schedule, pin status, region, and date range. Live updates show new deliveries while the dashboard is open.
Follow the route of a Letterflow
Open a Letterflow result to see its frozen graph and the path that actually ran. Select a component to inspect its input, output, status, and timing. Each Letter step also shows its recorded HTTP version when available.
Both Condition branches remain visible, but only the taken branch is highlighted. False is a successful comparison; a failed request or evaluation stops the run. Skipped components do not have invented outputs. Inspecting history never sends a request or reevaluates an expression.
Keep the deliveries that matter
Pin a result
Pinning protects the entire retained run from automatic expiry and normal FIFO removal, including its intermediate content. Pinned entries still count toward storage capacity. Clearing the Letterbox keeps them; explicit deletion removes them.
Watch the original deadline
Unpinning restores a deadline measured from the original result storage time. Old content can expire immediately. Pinning cannot bring back content that already expired.
- Tinkerer: 14 days
- Aspiring: 60 days
- Coder: 180 days
Retention covers headers, URLs, detailed errors, expressions, intermediate results, and frozen definitions as well as bodies. After expiry, detailed content is unavailable even if a minimal history row remains.
Unpinning an expired result requires confirmation: its retained content becomes unavailable immediately and eligible for permanent cleanup. Pin controls remain locked during the request and for two seconds afterward.
Make room for the next delivery
At normal capacity, the oldest unpinned entry makes room for a new one. Pinning must leave room for incoming results. If nothing can be removed, execution can finish without retaining new content.
Older overflow entries become read-only. When retained entries exceed the new allowance, new result storage stays frozen until deletion brings the count strictly below the cap, or an upgrade fits all entries. Runs can still execute and consume quota; the dashboard reports when content was not stored.