Our App Details are:
Client ID: puc2D_c9Raaxxs4UxGzNOg
App Name: CalDotCom
Whenever a request to get a new access token times out the refresh token is no longer valid and it starts returning an invalid_token (i.e. invalid refresh token) error as the failure reason.
We need to be able to retry with the last token because of failure reasons like this. A tolerance of 2 or 3 refresh token being valid concurrently will be highly appreciated. This app is used to manage meeting bookings across our entire organisation from our booking tool and this failure breaks the system both our team members and clients don’t get any meeting links after bookings occur or can no longer have meetings booked this is crippling many processes.
Kindly treat as urgent.
@systemProc @seanbuffer ,
Are you two coordinating efforts and requesting token tolerance increases for prod and dev apps?
1 Like
Exactly. That’s what we’re up to
Hi @systemProc @seanbuffer ,
I learned we don’t use token tolerance mechanism for OAuth apps now.
A refresh token can be used to fetch a new access token and refresh token again and again until it expires after 90 days. The refresh token does not becomes invalid after it is used to fetch a new access token and new refresh token. The refresh token becomes invalid only in these three conditions:
- refresh tokens expired ( after 90 days)
- customer uninstalls the app
- customer reauthorized the app
They checked the 15 day call log for the client id and saw some API calls to fetch a new access token using the refresh token failed because either of the following reasons:
- User has reauthorized but customer made the API call with old refresh token. Since user has reauthorized that old refresh token is revoked or became invalid now.
- Incorrect refresh token value. The refresh token sent in API call doesn’t have valid JSON format.
Hi @gianni.zoom,
Noted with thanks. We’ll harden our system around the stated behavior.
1 Like
