FlowRelay
Operate
Event lifecycle
Use lifecycle states to understand what FlowRelay has proved. Do not read them as a claim about downstream Shopify Flow actions.
Lifecycle states #
Use lifecycle states to understand the boundary FlowRelay has reached for a specific event.
| State | What it proves | Next safe action |
|---|---|---|
| Accepted | FlowRelay authenticated and durably stored the event before responding. | Wait for processing to reach a terminal outcome before replaying or resending. |
| Queued or processing | FlowRelay is still working toward a terminal handoff result. | Wait; do not replay or ask the sender to resend while processing is still active. |
| Delivered | FlowRelay handed the trigger to Shopify Flow. | Inspect Shopify Flow separately if a branch or downstream action did not behave as expected. |
| Failed | FlowRelay reached a terminal validation, mapping, readiness, or handoff failure recorded by the receipt and support code. | Follow the support code; use sender resend for rejected input or preview replay only when retained material and current setup make replay safe. |
| Rejected | FlowRelay did not accept a trusted replayable event because authentication, JSON, size, or another intake requirement failed. | Correct the sender request and send a fresh event; there is no accepted event to replay. |
| Waiting to retry | FlowRelay is retrying the Shopify Flow handoff on its own schedule. | Wait; no operator action is required yet. |
| No workflow | FlowRelay could not find a matching enabled Shopify Flow workflow. | Enable the matching Shopify Flow trigger, then preview replay if the event is retained. |
| Duplicate suppressed | FlowRelay identified a repeated external event ID for the same endpoint inside the dedupe window. | Open the linked first receipt and confirm whether the repeated send was expected. |
| Manual review | FlowRelay paused automatic recovery because Shopify Flow may already have received the handoff. | Review diagnostics and the replay preview before approving any second handoff. |
| Replayed | A deliberate second attempt was made from retained event material. | Inspect the linked replay attempt; the original receipt outcome is not rewritten. |
Manual review #
Manual review means FlowRelay paused automatic recovery because Shopify Flow may already have received the handoff, so a duplicate Shopify Flow action could run. Use diagnostics and the replay preview before approving any second handoff.
Retry and reconciliation #
FlowRelay may reconcile accepted events that have not reached a terminal outcome. It does not expose merchant-configurable retry schedules or retry policy controls.
Use the receipt for recovery #
The receipt gives the support code, replay availability, diagnostics state, and safe next action for the event's current lifecycle state.
Operating guidance
Apply the concept through the receipt before changing setup, resending, or replaying.
-
Start with the receipt outcome: Accepted, Delivered, Failed, No workflow, Duplicate suppressed, or Rejected.
-
Read the timeline to see whether FlowRelay stored the event, queued processing, evaluated duplicate suppression, attempted the Shopify Flow handoff, or recorded a terminal result.
-
If the receipt says FlowRelay is waiting to retry, let FlowRelay make the next automatic handoff attempt instead of replaying or asking the sender to resend.
-
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.
-
Treat No workflow as a setup/readiness problem: enable the matching Shopify Flow trigger, then preview replay while retained.
-
Treat Duplicate suppressed as a sender retry or repeated external event ID that FlowRelay blocked from a second automatic handoff.
-
Treat Manual review as a side-effect caution: review diagnostics and the replay preview before approving a second handoff.
-
Use the recovery code and safe next action before replaying, resending, or changing endpoint configuration.
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.