On this page
Why a deployed extension can still fail to appear
Installation, deployment, and placement are prerequisites, but they do not guarantee that the extension mounts at runtime. A current app version may fail only on a particular checkout target, store configuration, or customer account page. A successful local build cannot catch every runtime data assumption. Shopify’s new telemetry gives developers evidence of mount failures that previously looked like random missing blocks.
Where to find the evidence
- Open the app in the Dev Dashboard.
- Under Operations, inspect Extension mount failure rate for the selected date range.
- Open Top extension installations by failure rate to identify the stores and targets with the worst current-version failures. Shopify ranks installations with at least ten loads.
- Follow a row to its mount failure logs, or open Logs and filter the new UI extension events by store, extension, target, and result.
- Correlate the failure with the extension version, recent deployment, target, and the data that page expects.
Fix the cause, not just the symptom
Reproduce the failing target with the same market, buyer state, and cart conditions. Check for unhandled missing fields, incorrect assumptions about cart lines or customer data, exceptions during initial render, and target-specific API availability. Add defensive rendering for optional data, but do not silently hide a required business rule. If the extension controls a mandatory checkout restriction, enforce that rule with the appropriate server-side validation mechanism rather than depending on a UI block loading.
Understand the numbers
These metrics count failures attributed to your app. Shopify says failures caused by Shopify itself, the network, or the buyer’s browser are excluded. A low mount failure rate is therefore not proof that every shopper saw the extension. The merchant-facing health status and alerts described in the November 6 announcement were coming soon, not a currently available merchant dashboard feature to depend on.
How to test this
- Record the app version and exact checkout/customer-account target before changing anything.
- Compare a known-good store and a failing store using the same date window in Operations.
- Filter UI extension events to the failing store and target; inspect the error details.
- Reproduce the issue with a representative buyer and cart; fix the underlying runtime exception.
- Deploy the corrected app version and repeat the same checkout or account journey.
- Check mount failures over a comparable period after release, while accounting for low-volume installations.

