The event was Delivered and the unresolved failure happened later.
Continue in Shopify Flow or the downstream system instead of repeating the handoff.
FlowRelay
Recover deliberately
Replay gives a retained event another handoff. It can also repeat emails, tags, app calls, fulfillment work, refunds, or partner notifications. Review the business effect before you repeat the transport.
Replay is a recovery action. It is not a general-purpose resend button and it does not repair a failure that happened after Shopify Flow already received the trigger.
The original handoff result is the first decision boundary.
Continue in Shopify Flow or the downstream system instead of repeating the handoff.
Resolve the uncertainty before a production replay. A newer configuration may change what the event does now.
Use the replay preview and confirmation path so the actor, reason, and result stay visible.
A replay starts from retained event context but runs against current endpoint and workflow conditions.
| Review | Original event | Current state |
|---|---|---|
| Receipt facts | Sender, endpoint, trigger family, mapping, and handoff result. | Confirm you are acting on the intended retained event. |
| Configuration | Settings and readiness recorded when the event arrived. | Endpoint settings and Shopify Flow readiness that apply now. |
| Business effects | Actions that may already have happened. | Actions, deduplication behavior, and partner effects that could repeat. |
Read the original receipt and why the handoff needs another attempt.
Check present readiness, configuration drift, duplicates, and side effects.
Use the governed replay path rather than improvising another sender request.
Retain the actor, reason, replay result, and later support context.
If the event belongs in Shopify Flow again, use the original receipt, current readiness, side-effect review, and confirmation path together.