We’ve implemented a significant enhancement to how refresh tokens are managed, particularly for concurrent API calls in distributed environments. This improvement ensures greater stability and efficiency when refreshing access tokens.
What’s Improved?
Concurrent Refresh Token Call Handling:
To optimize performance and prevent race conditions in distributed systems, we’ve refined our refresh token mechanism. Now, if multiple concurrent calls are made within a 30-second window using the exact same client_id and client_secret and refresh_token combination, the system will return the same refresh token for all these calls.
Why was this enhancement necessary?
This enhancement is targeted to help large-scale developers who have distributed systems:
- Improve Stability: Reduces the likelihood of invalidating refresh tokens prematurely due to concurrent requests from different services or instances.
- Simplify Distributed Architecture: Makes it easier to manage token refreshing in environments where multiple services might simultaneously attempt to refresh tokens.
Note
: No changes are required on your end to benefit from this enhancement. It is automatically applied to all relevant API interactions.Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article