FlowRelay
Recover
Replay an event
Replay can create downstream side effects. Treat it as an explicit recovery action, not an automatic retry button.
Recovery steps
Complete these checks before executing a recovery action.
- 01Open the receipt and confirm the original request is still retained and replayable.
- 02Compare the original receipt facts with current endpoint authentication, mapping, and Shopify Flow readiness.
- 03Review possible downstream side effects, including duplicate workflow actions.
- 04Preview the replay intent and confirm the target event, endpoint, current configuration, and idempotency details.
- 05Execute replay only when the operator or authorized agent has the required authority.
Replay prerequisites #
Replay requires a retained replayable event, current endpoint configuration that is safe to use, matching Shopify Flow readiness, operator or agent authority, and an explicit preview before execution.
Preview checklist #
Before executing replay, confirm the original event, endpoint, current event type, mapping, workflow readiness, possible downstream side effects, idempotency key, and audit attribution.
When not to replay #
Use a sender resend or manual investigation instead when replay would be unsafe.
| Situation | Safer action |
|---|---|
| Raw retained event material expired | Ask the sender to send a fresh event. |
| The source payload was wrong | Fix the source payload and resend from the sender. |
| Downstream actions may duplicate customer-visible work | Inspect Shopify Flow, adjust the workflow, or get human approval before replay. |
| The grant or role does not allow replay | Escalate to an authorized human operator. |
Delivered means FlowRelay handed the trigger to Shopify Flow. It does not mean downstream Shopify Flow branches, app calls, fulfillment changes, emails, or later systems completed.