Replay an event

# Replay an event

Canonical: https://docs.flowrelay.app/recover/replay/
Markdown: https://docs.flowrelay.app/recover/replay.md

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.
1. Confirm replay availability
   Open the receipt and confirm the original request is still retained and replayable.
2. Compare current setup
   Compare the original receipt facts with current endpoint authentication, mapping, and Shopify Flow readiness.
3. Assess downstream side effects
   Review possible downstream side effects, including duplicate workflow actions.
4. Preview the replay
   Preview the replay intent and confirm the target event, endpoint, current configuration, and idempotency details.
5. 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.
6. 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: Raw retained event material expired; Safer action: Ask the sender to send a fresh event.
- Situation: The source payload was wrong; Safer action: Fix the source payload and resend from the sender.
- Situation: Downstream actions may duplicate customer-visible work; Safer action: Inspect Shopify Flow, adjust the workflow, or get human approval before replay.
- Situation: The grant or role does not allow replay; Safer action: Escalate to an authorized human operator.

## Handoff Boundary
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.

## Related
- [Retries, replay, and resend](https://docs.flowrelay.app/recover/retries-replay-and-resend.md)
- [Action previews](https://docs.flowrelay.app/reference/action-intents.md)
- [Grants and scopes](https://docs.flowrelay.app/agent-access/grants-and-scopes.md)

## Safety Boundary
Do not share endpoint secrets, authentication headers, HMAC values, tokens, raw event bodies, customer records, Shopify sessions, store passwords, or database URLs in public examples.