Operate

Retention

FlowRelay keeps receipt evidence for investigation, but retained event bodies 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 event body	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 the raw event body is gone.
Diagnostics shares	Share a new diagnostics share from current safe facts if support still needs evidence.
Dedupe keys and action-preview records	Duplicate suppression and preview execution safeguards follow their own bounded windows.

Replay is available only while FlowRelay still has retained replayable event material and the current operator or agent has authority.

When retained material is gone, do not rebuild raw event bodies from screenshots, chats, tickets, or memory. Use a fresh sender-side resend.

Apply the concept through the receipt before changing setup, resending, or replaying.

Open the receipt and check whether the source event body is retained, expired, or was not retained.
Use replay only while FlowRelay still has retained replayable event material.
When replay is unavailable, ask the source system to resend a fresh event instead of reconstructing raw event bodies.
Use diagnostics to share redacted receipt and setup facts, not raw retained bodies.
Remember that retention is plan-bound: cleanup also removes diagnostics shares, dedupe keys, replay-preview records, support summaries, and grants that have already expired.