Dev Dashboard / UI Extensions / Monitoring

In Dev Dashboard,
you can now see UI Extension "load failures"

Dev Dashboard now shows how often your app causes Checkout and Customer Account UI Extensions to fail to load, and on which stores. Health statuses and alerts are also expected to appear for merchants soon.

What's on this page
  1. What's changing? (30-second overview)
  2. How it works: from failure detection to delivery
  3. 3 things you can see in Dev Dashboard
  4. Failures that count / failures that don't
  5. Coming soon: health status for merchants
  6. What to do now (3 steps)
  7. 5 key points for developers
  8. 3 practical use cases
  9. One-line summary for client proposals

1What's changing?

When a UI Extension fails to load, buyers don't see the experience you built, and app developers have had a hard time noticing.
With this update,Dev Dashboard surfaces these "mount failures", so you can identify causes and ship fixes faster.

Before: failures go unnoticed

If an extension fails to load, it simply disappears from the buyer's screen, making the problem hard for developers to spot.

Now: see failure rates, stores, and logs

Operations on your app's home shows the failure rate and a ranking of installs with the most failures, while Logs records failure events.

Applies to: Checkout UI Extensions Customer Account UI Extensions

2How it works: from failure detection to delivery

Not displayed Buyer's screen Checkout / customer accounts Identifying the cause Caused by the app → counted Other causes → excluded Failures caused by Shopify, the network, or the browser aren't counted Dev Dashboard (developers) Extension mount failure rate Installs with high failure rates UI extension events in Logs Settings > Apps (merchant) • Status based on loads in the last 7 days • Warning / Critical Coming soon At Critical Alert in the admin Catch and fix issues first
Mount failureWhat it is: a failure that occurs while an Extension is being loaded and displayed on the buyer's screen. In this case, only failures caused by the app are counted.

33 types of information in the Dev Dashboard

Operations

Extension mount failure rate

How many times the Extension loaded during the selected period, and what percentage of those loads failed.

Operations

Installs with the highest failure rates

Top extension installations by failure rate.The current versionof the Extension, ranked by the stores and Extension targets where it fails most. Only installs with 10 or more loads are included. Each row links to that store's mount failure logs.

Logs

UI extension events

A new event is recorded each time a mount fails.store/extension/target/result can be used to filter.

4Which failures count and which don't

Counted

App-caused failures

Only app-caused failures are reflected in the failure rate, rankings, and Logs.

Not counted

Failures not caused by the app

Shopify Network Buyer's browser

These are excluded from the metrics and don't appear in Logs.

The article doesn't explain how a failure is judged to be "app-caused" or which specific errors qualify.

5Coming soon: health status for merchants

Merchants will also be able to use Settings > Apps to see the same health information for the Extensions installed on their store. The current version of each Extension gets a status based on itsloads over the last 7 days.

No rating Fewer than 10 loads per week No status assigned Warning When failures are confidently above 5% for for 3 days persisted Critical Confident that over 50% are failing for 2 days persisted Insufficient data Failure rate > 5% Failure rate > 50% → admin alert
StatusFailure rate conditionDurationImpact on merchants
Not evaluated Fewer than 10 loads per week — No status shown
Warning Confident that over 5% are failing 3 days Status shown in Settings > Apps
Critical Confident that over 50% are failing 2 days Status shown + alert in the Shopify admin
Critical alert recipients : Store staff who can view reports and have access to the app. No release date given (only "coming soon").

6What to do now (3 steps)

1

Open your app's home in the Dev Dashboard

Check Extension mount failure rate in the Operations section.

2

Identify the stores/targets with the most failures

Go from a ranking row to that store's mount failure logs.

3

Filter in Logs and fix

Filter by store/extension/target/result to trace the cause.

The post's call to action: "Check and fix issues in the Dev Dashboard now, before merchants see them.".

75 key points for developers

App

1. Only app-caused failures are counted

Failures caused by Shopify, the network, or the browser are excluded. The metric assumes any failures shown can be treated as issues in your own code.

v.now

2. Only the current version is evaluated

Both the ranking and the merchant-facing status apply to the extension's current version. After you release a fix, evaluation appears to be based on loads of the new version.

≥10

3. "10 loads" is the threshold

The ranking only includes installations with 10 or more loads. For merchants, fewer than 10 loads per week means no evaluation. Low-traffic stores are less likely to show numbers.

4. Isolate issues by target

Rankings are broken down by "store × extension target," and Logs can also be filtered by target. Use this to pinpoint failures that happen only in a specific placement.

3 days 2 days

5. Left unchecked, merchants will see it, so the grace period is short

If the failure rate stays above 50% for 2 consecutive days, it becomes Critical and an alert appears in the merchant's admin.a routine of checking the Dev Dashboard after each deploymentUnless you build in this routine, you'll only find out when merchants contact you. The article doesn't say whether this metric is available via API or webhooks.

83 practical use cases

deploy
USE CASE 1

Add "mount failure rate" to your post-release checks

Problem
After updating a Checkout UI Extension, you may not notice that it isn't rendering on some stores in production.
Action
Add the Dev Dashboard's Extension mount failure rate to your post-deployment checklist, and compare date ranges before and after the release.
Result
Catch anomalies before they reach Warning or Critical, and fix them before merchants see anything.
Technical notes
Evaluation is per current version. Right after a release, load counts are low, so check the rankings after at least 10 loads have accumulated.
store target result
USE CASE 2

First-pass triage for "it doesn't show up on this one store" inquiries

Problem
When a merchant reports that "the app isn't showing up in checkout," you can't reproduce it and the investigation drags on.
Action
Filter UI extension events in Logs by store and target to check whether mount failures were recorded for that store.
Result
If failure logs exist, investigate it as an app-side issue; if not, triage on the assumption that the app may not be the cause.
Technical notes
Failures caused by Shopify, the network, or the browser are not logged by design. Note that "not in the logs" doesn't necessarily mean "it rendered."
Healthy Warning Critical
USE CASE 3

Review the health of installed apps together with merchants on build projects

Problem
Checkout and customer accounts have extensions from multiple apps, but the operations team can't see which ones are working properly.
Action
Once the merchant-facing view is released, add the status under Settings > Apps to your regular operations checklist. Also confirm which staff permissions receive Critical alerts.
Result
Spot faulty apps early and contact app vendors with concrete evidence.
Technical notes
Alerts go to staff who have both "permission to view reports" and "access to that app." No release date has been announced.

9One-line summary for proposals

"For Checkout / customer account UI extensions,see how often they fail to load because of the app
can now be tracked down to the store and target level in the Dev Dashboard.
Merchants will soon see these as Warning / Critical too, so check and fix them now."