Replay external events into Shopify Flow safely.

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.

Stop, pause, or consider replay.

The original handoff result is the first decision boundary.

Stop

The event was Delivered and the unresolved failure happened later.

Continue in Shopify Flow or the downstream system instead of repeating the handoff.

Pause

Current readiness, configuration, or duplicate effects are unclear.

Resolve the uncertainty before a production replay. A newer configuration may change what the event does now.

Consider replay

The retained event needs another handoff and the consequences are understood.

Use the replay preview and confirmation path so the actor, reason, and result stay visible.

Compare the original event with the world it will enter now.

A replay starts from retained event context but runs against current endpoint and workflow conditions.

Original and current context to review before replay
ReviewOriginal eventCurrent state
Receipt factsSender, endpoint, trigger family, mapping, and handoff result.Confirm you are acting on the intended retained event.
ConfigurationSettings and readiness recorded when the event arrived.Endpoint settings and Shopify Flow readiness that apply now.
Business effectsActions that may already have happened.Actions, deduplication behavior, and partner effects that could repeat.

Keep recovery deliberate and auditable.

  1. Inspect

    Read the original receipt and why the handoff needs another attempt.

  2. Assess

    Check present readiness, configuration drift, duplicates, and side effects.

  3. Preview and confirm

    Use the governed replay path rather than improvising another sender request.

  4. Keep the record

    Retain the actor, reason, replay result, and later support context.

Review before retrying the handoff.

If the event belongs in Shopify Flow again, use the original receipt, current readiness, side-effect review, and confirmation path together.