Replay external events into Shopify Flow safely.

Replay is valuable because it gives a second chance. It is risky because Shopify Flow may repeat real business actions.

A retry button can feel reckless without context.

The person replaying the event needs to know whether the original event was accepted, what settings were active, whether the workflow is ready now, and what downstream effects could repeat.

FlowRelay makes replay something you review first.

Replay starts from retained event context and receipt facts, shows what to check first, and keeps audit history so recovery does not become invisible improvisation.

Replay preview checklist

The useful evidence is a cautious preview, not a claim that every event is safe to retry.

Original facts Sender, endpoint settings, trigger family, mapping, and original handoff result are visible.

Replay should begin from the event that actually happened.

Current state Current endpoint settings and Shopify Flow readiness are checked.

A replay runs against the world as it exists now, not only as it existed then.

Side effects Duplicate actions are considered before execution.

The cost of replay is usually downstream, not at the intake layer.

Replay can repeat business actions.

Shopify Flow may send emails, call apps, create tasks, tag customers, start fulfillment work, or trigger partner systems. Treat replay as recovery, not as a casual resend.

Common questions.

Can replay create duplicates?

Yes — that is the risk to manage. Replay can repeat downstream Shopify Flow actions, so review side effects before replaying real events.

When should I not replay?

Do not replay when the event already reached Shopify Flow and the remaining issue is a downstream action that should be handled in Shopify Flow or another system.

Review before retrying the handoff.

Use the original receipt, current Flow readiness, and side-effect check before sending the event again.