Troubleshooting

Resolve common source, domain, routing, and checkout readiness issues.

Updated August 10, 2026
On this page
Before you start
  • The exact Funnel name and current readiness reason
  • Access to the relevant Shopify, DNS, or gateway account

Start with the computed readiness reason in the Funnel editor. Fix dependencies from the bottom up: published Source Page and supporting Pages, Delivery Setup, MID, pool, router policy, Funnel hostname, published Checkout, then save the Funnel graph.

Funnel is blocked

Open Funnel validation

Open Funnels, select the blocked Funnel, and read the named validation issue. Do not pause and resume dependencies to hide the message; fix the underlying configuration.

Follow the dependency chain

For payment routing, open the router selected in the Funnel, its published policy, assigned pool, and configured MID. For Shopify, verify the Source Page connection and scopes. For a custom hostname, compare both the TXT ownership and CNAME records before choosing Check connection. For a managed hostname, choose Retry setup and read the routing, HTTPS, or checkout-origin error.

Fast diagnosis

SymptomCheck first
Shopify products do not loadShopify Source Page connection and product-reading scopes
Domain remains DNS pendingFunnel's TXT and CNAME values plus DNS TTL
Domain remains HTTPS provisioningCNAME still resolves correctly and certificate provisioning has had time to complete
Managed domain remains ActivatingRetry setup and inspect routing, HTTPS, and checkout-origin status
Pool is UnavailableEnabled pool plus at least one healthy, configured MID
Router is DegradedStraight-sale and subscription pool readiness
Funnel is BlockedPublished Pages and Checkout, hostname, Funnel router, saved graph, Thank-you Page, and delivery readiness
Test payment is unexpectedFixed Dry Run card number and MID routing
Funnel says “waiting for published resources”Publish every referenced Page and Checkout; the Funnel refreshes automatically
Graph thumbnail is missingConfirm the Page or Checkout is published, then allow its cached screenshot job to finish

Common issues