We’re experiencing an issue with the Partner Dashboard’s API health warnings not clearing after we’ve already resolved the underlying problem.
The situation:
Our app received a “Fix overdue” warning on March 31, 2026 related to the Market.currencySettings GraphQL field becoming nullable in API version 2025-04. The warning states we need to “Update to version 2025-04 or later.”
We identified and fixed the issue the same day (March 31) - we updated our code to properly handle the nullable Market.currencySettings field.
The problem:
It’s now April 23, 2026 - almost a full month later - and:
The “Fix overdue” warning still appears in our Partner Dashboard with the same “Last detected” date of March 31, 2026.
More importantly, merchants still see a banner on our app’s page in their Shopify Admin saying: “Update required for new Markets - The app developer needs to update this app to support new Markets. Contact the developer.”
This is concerning because:
The warning is creating unnecessary alarm for our merchants
It damages trust in our app - merchants think we haven’t addressed the issue when we actually fixed it within hours
We have no way to manually clear or re-trigger the detection
The official documentation states warnings should clear within a 14-day rolling window. The warning has persisted for 24 days.
Questions for Shopify:
How frequently does Shopify re-scan apps to detect whether API deprecation issues have been resolved?
Is there a way to manually trigger a re-check or clear a stale warning?
What criteria does Shopify use to determine the warning should be removed? Is it based on actual API call monitoring, or the declared API version in the app config?
Is there a way to remove the merchant-facing “Update required for new Markets” banner sooner, so our merchants aren’t unnecessarily concerned?
Has anyone else experienced this? Any insight from the Shopify team would be greatly appreciated.
Hey @markkkkas - thanks for reaching out. Those warnings should only remain for 14 days after the last call that triggered it was made. We have some documentation here that should answer some of your questions, so just sharing in case it helps:
When it comes to the Markets compatibility banner specifically though, the clearing window for that one is a little longer than the standard 14 days on the API health report. The detection for Markets runs on its own rolling window, so there can be a bit of a lag between when you deploy a fix and when the merchant-facing banner drops off, even after the API health status itself updates.
If you’re open to sharing your app ID (or client ID), I’m happy to look into this further on our end here to see where things stand for your specific app, as it is a little odd that the general deprecated API call warning message is lasting longer than 2 weeks.
I have seen old, fixed overdue warnings persist past 14 days and, more recently (start of April) I saw a fixed warning re-appear for App A when a new warnings appeared for App B. This only lasted for a day of so.
These warnings really need to include an IP address as I have seen it fixed in the app but someone runs a utility script or command-line program that causes it to reappear, and everyone is confused because it was fixed in the app for weeks or months.
Nevertheless, let’s all just hope the “app not supported” message is no longer being displayed to shops as this was inaccurate and confusing.
Hey @sshaw - thanks for flagging as well. Good idea on including IP addresses - I can pass that along as a feature request for sure. Can’t guarantee anything on that front in terms of implementation, but if we surfaced those in the Dev Dashboard for instance, I can’t think of any privacy reasons not to (as opposed to surfacing it in the merchant admin).
If the “unsupported” flag clears in the partner dashboard, that does correlate with its appearance in merchant admins too, but if you notice you’re still seeing any odd behaviour with these just ping me here and I can take a look.
I can pass that along as a feature request for sure. Can’t guarantee anything on that front in terms of implementation,
I have suggested this to Partner Support since day 1 so not holding my breath.
If the “unsupported” flag clears in the partner dashboard, that does correlate with its appearance in merchant admins too,
This should not be shown to merchants at all. It’s a lie. The app is supported and even after the deadline passes it’s still supported until you guys “flip the switch”. All it does is cause confusion. We would get panic emails all the time asking if the app is supported.
Thanks for the follow-up. I had a chance to take a look at the app on my end, and I’m digging into this internally given things have been well past the standard window for the warning to clear at this point.
I’ll loop back here as soon as I have something concrete to share. Just to set expectations though, I can’t guarantee a timeline on this one, but I’ll make sure your case is being looked at.