FlowRelay Docs Shopify Flow
All docs pages

START

USE CASES

SET UP

OPERATE

RECOVER

AGENT ACCESS

REFERENCE

Markdown

Event history

Plain Markdown for agents, CLIs, MCP clients, and readers who want a copyable text version.

# Event history

Canonical: https://docs.flowrelay.app/operate/event-history/
Markdown: https://docs.flowrelay.app/operate/event-history.md

Event history is the operator's scanning surface before opening the full receipt.

## How to use this page
Use this order when you are checking what happened to an event.
1. Open Event history in FlowRelay.
2. Filter by endpoint, event type, outcome, or approximate time window.
3. Open the receipt for the event that needs attention.
4. Check the receipt outcome, recovery code, retention state, and replay availability.
5. Share the receipt summary or diagnostics package when help is needed. Avoid copying private request data into external channels.

## Find the right event
Filter by endpoint, event type, outcome, and approximate time window. Open the receipt before deciding whether to wait, fix setup, replay, resend, or share diagnostics.


## History outcomes
Read history statuses as FlowRelay event-boundary outcomes, not as claims that downstream Shopify Flow actions finished.


- Outcome: Delivered; What to do next: Inspect Shopify Flow if a branch or downstream action did not behave as expected.
- Outcome: Failed or no workflow; What to do next: Open the receipt, fix the setup or workflow readiness, then preview replay if retained.
- Outcome: Rejected; What to do next: Fix sender auth, JSON, or required fields and ask the sender to send a fresh event.
- Outcome: Duplicate suppressed; What to do next: Open the linked first receipt and confirm whether the repeated send was expected.

## Safe sharing
Share a receipt summary or diagnostics package when help is needed. Avoid copying raw request material into external tools.


## 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
- [Event lifecycle](https://docs.flowrelay.app/operate/event-lifecycle.md)
- [Retention](https://docs.flowrelay.app/operate/retention.md)
- [Error codes](https://docs.flowrelay.app/recover/error-codes.md)

## Safety Boundary
Do not include raw payloads, endpoint secrets, auth headers, HMAC values, Shopify tokens, Shopify sessions, database URLs, customer data, merchant incidents, or copied private logs in public examples.