More resilient refreshes for expiring offline access tokens
doc:019fb619-9b4a-74ac-a83e-3ffa98844fb4::feed/https://shopify.dev/changelog/more-resilient-refreshes-for-expiring-offline-access-tokens- Product
- Shopify Admin GraphQL API
- Source
- Feed
- Change kind
- Feed Entry
- Detected
- Last updated
Interpreted documentation change
What the vendor announced
The bulletin describes an enhancement to token refresh behavior for offline access tokens: refreshes now retain the previously used refresh token until the app starts using its replacement, improving resilience if a refresh response is lost or not persisted. No migration is required, but apps should atomically store every refreshed token pair. It notes a previous behavior where a refresh could be retried for up to 60 minutes after use. There is no explicit deadline or endpoint replacement provided.
More resilient refreshes for expiring offline access tokens Expiring offline access token refreshes now retain the previously used refresh token until an app begins using its replacement. This rollout helps apps recover when a refresh response is lost or isn’t persisted. No migration is required, but apps should continue to store every refreshed token pair atomically. What changed Previously, after an app used a refresh token, it could retry that token for up to 60 minutes. If the app didn’t receive or save the newly returned access token and refresh tok…
Monitored for you
Does this change affect your integration?
Choose the operations and fields your services use. Detektu matches Shopify findings to that declared usage so your team can review the relevant evidence. No agent or repository access required.
Multi-source correlation
Related changes
Other Shopify findings correlated with this change across sources.
- DeprecationSDK version 12.2.0 yanked
sdk:npm/@shopify/shopify-api@12.2.0 - InfoSDK release 14.0.1
sdk:npm/@shopify/shopify-api@14.0.1 - InfoSDK release 14.0.1
sdk:npm/@shopify/shopify-api@14.0.1