FlowRelay
Operate
Retention
FlowRelay keeps receipt evidence for investigation, but retained event bodies and recovery surfaces have explicit windows.
What retention affects #
The current Shopify Flow edition uses a 30-day window for event history, retained accepted-event bodies, and created diagnostics shares. Replay eligibility depends on retained replayable material plus current setup, authority, and safety checks; it is not guaranteed merely because a receipt is visible.
| Material | Current duration | After it expires |
|---|---|---|
| Retained event body | 30 days from accepted intake | Replay is unavailable. Ask the sender to send a fresh event if recovery requires the original content. |
| Receipt and event-history record | 30 days | The event leaves the current public history window; retain only support-safe references your own process is allowed to keep. |
| Diagnostics shares | 30 days from share creation | Share a new diagnostics share from current safe facts if support still needs evidence. |
| Replay eligibility | At most the retained-body window, subject to receipt state and current safety/authority checks | Use a fresh sender-side event; do not reconstruct the raw body from screenshots, tickets, or memory. |
| Dedupe keys and action-preview records | Their own bounded contract windows | 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 event bodies 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.
-
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.