@J_J I believe there is a fair amount of smart people at Shopify. I think problem is the gatekeepers above them. Unfortunately many people favor money and career over moral and virtue.
This fix is too little, too late for us. This thread itself is older than your new 7-day grace period, so common sense should dictate that this update does absolutely nothing for the stores that are already orphaned. We ran our migration over a month ago, and your system permanently destroyed our tokens when the response dropped. How are we supposed to recover those? Forcing merchants to manually reinstall because your initial rollout lacked basic safety nets is unacceptable. What is the retroactive fix for the installs you already locked out?
Pinging you directly on this because we are still sitting in the dark regarding the installs that were permanently orphaned over a month ago.
The 7-day grace period is great for future migrations, but it does absolutely nothing to help the merchants whose tokens were already destroyed by the initial rollout. We cannot accept manual reinstallation as the solution to a Shopify system flaw. What is the concrete plan to retroactively recover the tokens for the installs you have already locked out?
@TerenceShopify I see that this dropped: More resilient token exchanges when migrating tokens without a user session - Shopify developer changelog
And I realize that I misread your previous message.
At first I thought you said that any refresh token would be valid for seven days.
This is actually true only for the initial migration from non-expiring to expiring (that’s where I mis-read it).
Issue: It does not seem to fix the concern that many of us have on the long term usage of it when something gets broken.
It will certainly help with the initial migration but the whole thing still seems to have fragile areas and I personally do not feel confident migrating to it yet.
Taking some notes here because we have all this wording and various consecutive updates so it’s getting hard to remember everything
- Non expiring offline token: The legacy tokens that we store once and can use forever to connect to the admin gql api. It’s gone forever after we’ve migrated to the new system.
- Expiring offline access token: The new tokens that are valid for
60 minutesto connect to the gql api as many times as we want in this period.- Once the 60 minutes are over it can no longer be used
- Refresh token: The new tokens that allows acquiring a new expiring offline access token and a new Refresh token.
- It’s valid until one of these condition is met:
- for
90 daysfrom the date it’s been request. - OR until the new expiring offline access token has been used.
- OR
30 daysafter it’s been used to acquire another refresh token (capped by the 90 days).- the last to bullets are explained here: More resilient refreshes for expiring offline access tokens
- for
- In other terms: using the new expiring offline access token from a given refresh token means we ackloledge that the refresh process worked properly and it gets retired.
- It’s valid until one of these condition is met:
Please correct if anything is wrong
Still waiting on a response here. The fact is, Shopify’s initial rollout destroyed production tokens for early adopters, and your recent patch provides zero relief for the stores already impacted.
We followed your migration timeline, your infrastructure dropped the response, and our merchants paid the price. Forcing us to tell paying merchants to manually reinstall because of an infrastructure flaw on your end is damaging our business. What is the technical remedy or escalation path for these orphaned installs?
This thread is like a ghost town as far as Shopify is concerned 
Very few companies are this bad at communicating, it’s actually impressive 