Operate
Read receipts
A receipt is FlowRelay's durable proof artifact for an accepted event and its Shopify Flow handoff attempt.
How to read a receipt #
Start with the outcome, then read the safe facts that explain what FlowRelay can prove.
| Receipt field | Meaning |
|---|---|
| Outcome | The current FlowRelay boundary result, such as Delivered, failed, no workflow, rejected, or duplicate suppressed. |
| Endpoint snapshot | The endpoint configuration FlowRelay used for the original event. |
| Auth and validation | Whether the request passed authentication, required paths, mapping, and event type checks. |
| Handoff status | Whether FlowRelay handed the trigger to Shopify Flow. |
| Retention and replay | Whether retained event material is still available for a deliberate replay. |
Delivered boundary #
Delivered means FlowRelay handed the trigger to Shopify Flow. It does not mean Shopify Flow branches matched, app calls ran, fulfillment changed, emails sent, or later systems completed.
Use receipts with agents #
Authorized agents use receipt facts and diagnostics rather than asking humans for raw payloads, full headers, secrets, tokens, or private screenshots.
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.
FlowRelay