Why did my Shopify Flow not run?

The most frustrating automation failure is the one that feels like it disappeared between systems. FlowRelay helps turn that feeling into a short list of places to check.

One question can hide several causes.

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 after handoff.

FlowRelay narrows the search.

Receipts show whether FlowRelay saw the event, verified it, accepted it, mapped it, and handed it to Shopify Flow. That makes the next troubleshooting step much less ambiguous.

Where to look first

Use the receipt state to ask the next right question.

No receipt The event is not visible in FlowRelay.

Start with the sender URL, current receiver path, DNS, network, auth placement, or whether the sender fired.

Failed receipt FlowRelay saw the event but rejected or could not map it.

Check authentication, required fields, trigger family, endpoint settings, and mapping errors.

Delivered FlowRelay handed the trigger to Shopify Flow.

Inspect Shopify Flow branches, conditions, downstream apps, and action results.

Useful diagnostics should be narrow.

A good support handoff names exactly what happened and includes redacted receipt facts. It should not require copying private payloads into a ticket.

Common questions.

What does Delivered mean?

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.

What should support see?

Support should see redacted receipt facts and support codes, not raw payloads, endpoint secrets, authentication headers, or customer data.

Use the receipt to choose the next check.

Open diagnostics, confirm the receipt state, then move to the sender, FlowRelay, Shopify Flow, or downstream app that actually owns the next question.