A checkout extension that fails to appear can leave a retailer asking its app supplier for evidence neither side has collected. Shopify’s 6 November Dev Dashboard update adds a more specific starting point: visibility into app-caused failures when checkout and customer account UI extensions mount.
The dashboard shows a failure rate and ranks installations with at least ten loads. Rows link to mount-failure logs. Those records cover app-caused failures; Shopify says failures originating in its platform, the network or the buyer’s browser aren’t included.
Ask for the affected installation
Start a support request with the store, the missing experience and the approximate time someone observed it. Include the extension target if the developer can identify it. Keep customer information out of the initial message.
Ask the supplier to inspect the app’s Operations section for the relevant period, then narrow the logs by store and extension. The goal is a traceable observation. A general statement that the app works elsewhere doesn’t resolve an incident on your installation.
Read the rate with its sample
Shopify’s announcement explains that the ranking applies to the current version of an extension. Record that version and the selected date range when sharing a result. A later deployment or a different period changes the question the figures answer.
Request the load count alongside the rate. Agree a review period with the supplier before deciding whether a change improved the result. For a quiet store, leave enough time to collect useful observations instead of repeatedly refreshing a chart.
Separate a missing record from a resolved fault
An empty app-failure view needs context because the announced coverage excludes several other causes. Ask what the team checked outside that view. Retain the original report and the supplier’s explanation until the retailer has verified the customer journey again.
Create a short incident record containing the observed symptom, the evidence reviewed and the next test. Give each unresolved check an owner. If the supplier can’t reproduce the problem, agree what to capture if it happens again, rather than closing the request with no follow-up.
Verify the experience after a change
In a suitable test setting, repeat the journey that originally failed and record the deployed version. Check that the expected interface appears and that its action completes. Our recommendation is to retain this result alongside the subsequent monitoring period.
The announcement labels merchant health information and alerts as coming soon. Verify their availability in your own environment before adding them to a support procedure; this update alone doesn’t confirm that every retailer can see them.
For teams also checking data integrations, our Shopify sync-checkpoint guide covers another way to make operational checks repeatable. Give the extension incident its own completion criteria: a tested journey, an accountable supplier and a record of anything still unexplained.