FlowRelay
Operate
Retention
FlowRelay keeps receipt evidence for investigation, but retained request material and recovery surfaces have explicit windows.
What retention affects #
Retention determines which recovery actions are still possible after an event arrives.
| Material | After it expires |
|---|---|
| Retained request material | Replay is unavailable. Ask the sender to send a fresh event if recovery requires the original content. |
| Receipt facts | Safe facts can remain useful for investigation even when raw request material is gone. |
| Diagnostics packages | Share a new diagnostics package from current safe facts if support still needs evidence. |
| Dedupe keys and action intents | Duplicate suppression and preview execution safeguards follow their own bounded windows. |
Replay availability #
Replay is available only while FlowRelay still has retained replayable event material and the current operator or agent has authority.
Do not reconstruct private data #
When retained material is gone, do not rebuild raw payloads from screenshots, chats, tickets, or memory. Use a fresh sender-side resend.
Operating guidance
Apply the concept through the receipt before changing setup, resending, or replaying.
- 01Open the receipt and check whether source request material is retained, expired, or was not retained.
- 02Use replay only while FlowRelay still has retained replayable event material.
- 03When replay is unavailable, ask the source system to resend a fresh event instead of reconstructing raw payloads.
- 04Use diagnostics to share redacted receipt and setup facts, not raw retained bodies.
- 05Remember that retention is plan-bound and cleanup also expires diagnostics shares, dedupe keys, action intents, support rollups, and expired grants.