Welcome to the RingCentral Community

Quick update for developers, we have began rolling out the fix to this solution in specific environments, and will continue until this rollout is scheduled to be completed on November 7th.

If your application begins experiencing any issues related to this topic during this phased rollout, please post those issues here with as much detail as possible (making sure to remove any sensitive information such as API keys, API secrets, etc...).

As part of this workaround, provided the authorization code trade request for a token is executed within three seconds, hopefully the authorization code is still valid.

If it is expired, I would recommend shortening the retry-delay to 2 seconds and see if that resolves the issue.

If that does not work, the appropriate authorization flow would be to consider the authentication attempt as failed, and to re-initialize the process for the end user (you could notify the user "we had a problem processing your authentication, please try again").

What did you do if the authorization code is already expired? Thanks John!