What does Delivered mean?
Delivered means FlowRelay handed the trigger to Shopify Flow. Shopify Flow still owns branches, downstream app calls, emails, fulfillment actions, and later outcomes.
Troubleshooting
Why did my Shopify Flow not run?
The most frustrating automation failure is the one that feels like it disappeared between systems. FlowRelay helps split the question into places your team can actually inspect.
Failure feels safer when it has an address.
No receipt, failed receipt, and Delivered each point somewhere different.
Diagnostics give helpers enough context without exposing sensitive material.
What changes
One question hides several failure boundaries.
The sender may not have sent the event, authentication may have failed, required fields may be missing, Shopify Flow may not have had the trigger ready, or a downstream action may have failed later.
How FlowRelay helps
FlowRelay narrows the search.
Receipts show whether FlowRelay saw the event, verified it, accepted it, mapped it, and handed it to Shopify Flow, while preserving the boundary around downstream Flow behavior.
Evidence to check
Failure boundary decision tree
Use the receipt to ask the next right question instead of opening every dashboard.
- No receipt
- Start with sender URL, DNS, authentication, network, or current receiver path.
- Failed receipt
- Check authentication, required fields, endpoint settings, and mapping errors.
- Delivered
- Move to Shopify Flow workflow branches, conditions, downstream apps, and action results.
How to start
Troubleshoot by boundary.
Turn a vague failure into a sequence of visible checks.
-
01
Look for the receipt
Confirm whether FlowRelay received the event at the expected endpoint.
-
02
Read the result
Check accepted, failed, no workflow, or delivered state and the support-safe explanation.
-
03
Check Shopify Flow readiness
Verify that the matching trigger family and workflow were ready when the event was processed.
-
04
Inspect downstream outcomes
If Delivered is present, continue inside Shopify Flow or downstream systems.
Questions
Common questions.
Do public examples need raw payloads or secrets?
No. Public proof should use receipt facts, endpoint settings, mapped fields, support codes, and redacted diagnostics. Do not include endpoint secrets, authentication headers, tokens, raw event bodies, customer data, or copied private logs.
When is this a good fit?
This is a good fit when external events are expected to trigger Shopify Flow and the team needs to know whether the problem is sender, FlowRelay, Shopify Flow, or a downstream action.