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.
-
Confirm replay availability
Open the receipt and confirm the original request is still retained and replayable.
-
Compare current setup
Compare the original receipt facts with current endpoint authentication, mapping, and Shopify Flow readiness.
-
Assess downstream side effects
Review possible downstream side effects, including duplicate workflow actions.
-
Preview the replay
Preview the replay intent and confirm the target event, endpoint, current configuration, and idempotency details.
-
Acknowledge duplicate-action risk
Explicitly acknowledge that replay can repeat Shopify Flow branches and downstream actions, then confirm only when the operator or authorized agent has the required authority.
-
Verify the replay result
After execution, open the replay result and linked receipt, then inspect Shopify Flow separately for any downstream outcome that matters.
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, resolved event type, mapping, workflow readiness, possible downstream side effects, idempotency key, audit attribution, and the operator's explicit side-effect acknowledgement. After execution, verify the replay result and linked receipt; check Shopify Flow separately for downstream behavior.
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. |
Custom endpoint configuration #
Automatic retries preserve the configuration accepted with the original event. A manual replay previews the current configuration and refuses confirmation if that version has changed. Public receipts and diagnostics omit expression literals and authentication settings. Custom-data sample previews are ephemeral and do not run Flow or use live-event allowance; configuration review and execution use existing action allowances. Custom values in retained delivery data follow the same plan retention and access rules as the rest of the event.
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.