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 downstream Shopify Flow branches, app calls, fulfillment changes, emails, or later systems completed.
Use receipts with agents #
Authorized agents use receipt facts and diagnostics rather than asking humans for raw event bodies, full authentication headers, secrets, tokens, or private screenshots.
Custom endpoint configuration #
Automatic retries preserve the configuration accepted with the original event. A manual replay previews the current configuration and refuses confirmation if that version has changed. Public receipts and diagnostics omit expression literals and authentication settings. Custom-data sample previews are ephemeral and do not run Flow or use live-event allowance; configuration review and execution use existing action allowances. Custom values in retained delivery data follow the same plan retention and access rules as the rest of the event.
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