One In Nine Store Apps Is Running Out Of Runway

Every Store listing publishes the family releases it is certified against. Taken together, on 14 August 2026, those figures say something the individual listings do not: half the partner catalogue is current on Australia, another 38% sits one release back—unremarkable three months after a GA—and 158 apps are certified to Yokohama and nothing newer. Yokohama is the oldest release still inside the supported window. When Brazil ships, that window slides and those apps fall out of it.

What is the n-3 rule?

A certified Store app must remain compatible with one of the last three family releases. Once an app's newest certified release falls outside that window—older than current minus three—the listing is automatically unpublished. It stops appearing in the Store, and no customer can find or install it.

ServiceNow documents the mechanics of recertification thoroughly: how to recertify for a new release without code changes, and how to do it with them. What the public knowledge base does not spell out is the consequence of letting it slide.

The practical effect is a rolling deadline nobody sends you a reminder about. Two family releases a year means the window moves twice a year, whether or not your roadmap has room for it.

Where the catalogue actually sits today

Australia is a young release: early availability began on 12 March 2026 and general availability followed on 5 May. Fourteen weeks on, being one release behind is normal rather than negligent—most publishers are mid-cycle, not in trouble.

1. 73151%

   Australia

   Current release

2. 55338%

   Zurich

   One back — normal mid-cycle

3. 15811%

   Yokohama

   Oldest still in the window

Nothing older than Yokohama appears anywhere in the catalogue—which is the rule working exactly as described. Apps that fell further behind are already gone.

What happens when Brazil ships?

Brazil is the next family release. ServiceNow's Early Release Program page puts early availability at mid-September 2026, and states that early availability runs at least 45 days ahead of general availability—which places GA in early November, the date ServiceNow staff have given in the community forum. When it arrives the supported window becomes Brazil, Australia and Zurich. Yokohama drops off the end, and with it the 158 apps whose newest certification is Yokohama—spread across 119 publishers.

Supported window today

1. Yokohamaoldest supported
2. Zurich
3. Australiacurrent

When Brazil ships

1. Yokohama158 apps drop out
2. Zurich
3. Australia
4. Brazilenters

The runway is shorter than the GA date suggests. A recertification without code changes still means upgrading a vendor instance, regression-testing the app on the new release and going back through review. With code changes it is a development cycle. Publishers who start when Brazil lands are starting late.

You do not have to wait for it to land. ServiceNow's early release programme lets technology partners build against the early availability build and submit for Store certification before market launch—so the work can start in mid-September, not November.

Not all 158 are equally neglected. Median time since last publish is fifteen months. But the tail is long: 34 of these apps have not been republished in over two years, and the oldest has not been touched in nearly nine years.

The split inside those 119 publishers

Those publishers are not one group. They split into two situations that look identical in the numbers and are nothing alike in practice.

74 of the 119 have nothing current at all. Every listing they own is stuck on Yokohama. For most of these the app is not a live product any more—there is no customer upgrading and pushing them for compatibility, so nothing forces the work. They are still paying to be in the partner programme, and still holding a listing nobody is maintaining.

The other 45 are actively maintaining a portfolio and have let specific apps lapse. They keep other listings current on Australia or Zurich, so this is not neglect—it is triage. Somewhere a decision got made, explicitly or by default, about which apps were worth the release cycle.

That second group shows what recertification pressure actually does to a small team. It does not cause a crisis. It causes quiet attrition at the edges of a product line.

Why apps fall behind: the portfolio maths

Look at the same catalogue from the other direction and the mechanism is obvious. 70 independent publishers with fewer than 200 staff are carrying 372 live certified listings between them. The largest single portfolio in that group is 37 apps, held by a company of under fifty people.

Every one of those listings needs a regression pass and a review submission on every family release. Twice a year. Indefinitely. It does not scale with headcount, it scales with the number of apps you have shipped—which is to say, with your past success.

Custom-table count makes it concrete. The apps sitting on Yokohama today define 1,585 custom tables between them. That is the retest surface: the data model somebody has to walk through and confirm still behaves on the new release. It is unglamorous work, it competes with the roadmap every single cycle, and it loses.

How to check where your own app stands

It takes a minute. Open your listing on the Store and look at the compatibility list on the version panel—the family names, not the version numbers. Then:

• Australia listed? You are current. Your next deadline is Brazil, in the ordinary way.
• Zurich newest? Normal position mid-cycle. You have room, but the work is now on the clock.
• Yokohama newest? You are on the last release inside the window. Brazil moves it. This one needs scheduling now, not after GA.

Then do the same for every app you own, not just the one you thought of first. The publishers most exposed are not the ones with a single neglected app—they are the ones with enough apps that a couple can slip without anybody noticing.

If you want the mechanics of review itself—what the certification team actually inspects, the realistic timeline, what it costs—that is covered in our ServiceNow app certification guide. For a concrete example of what a family release can change underneath a certified app, see what Australia did to the dictionary read-only checkbox.

What the figures cover

Every number on this page comes from the ServiceNow Store's own public listings as they stood on 14 August 2026: the partner catalogue, and the release compatibility, publish date and custom-table count each listing publishes about itself. 1,653 listings, 695 publishers.

Of those 1,653, some 211 carry no version compatibility at all. Checking each one against the Store's own listing data: 203 are pointer listings—offerings that send the customer to the vendor's own website rather than installing anything on an instance, so they have no version to declare. The other eight are installable apps that publish no compatibility at all. All 211 are excluded from every percentage on this page, which leaves 1,442 installable apps as the denominator.

Individual publishers are not named here. The aggregate is the useful part; a list of firms whose listings are about to lapse is not.