Hi all - we think the change we rolled out today will significantly increase the reliability of the token refresh system and address the concerns that have been raised on this thread and elsewhere as well. Please continue to provide your feedback as it’s been instrumental in helping us understand the concerns the developer community has about this change from non-expiring to expiring tokens. I’ve also posted about this change here with some more details.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Update: more resilient refresh-token recovery for expiring offline tokens | 3 | 284 | September 4, 2026 | |
| Please add recovery parity with refresh tokens | 25 | 845 | October 9, 2026 | |
| 520 during refresh_token rotation permanently orphans the offline access token | 16 | 1054 | July 21, 2026 | |
| Migrating from non expiring to expiring access tokens | 129 | 5085 | October 15, 2026 | |
| Action required: existing public apps must use expiring offline access tokens by January 1, 2027 | 33 | 2045 | September 17, 2026 |