500 "Internal Server Errors" while refreshing OA2 tokens

[aarondcoleman]

We're seeing a decent amount of 500 "Internal Server Error" responses while refreshing OA2 tokens. They do eventually resolve within a few seconds and using our retry backoff policy.

[IoanbsuFitbit]

@aarondcoleman, when did you start to see 500s?

Are you trying to send several requests to update your the same refresh token as the same time?

[aarondcoleman]

Hi @IoanbsuFitbit

It started at 12:46pm PST and is still ongoing. I don't believe we are sending concurrent requests, we do an immediate retry on the first attempt though.

--Aaron

[IoanbsuFitbit]

Hm, we don't have any changes to system that would line up exactly with 12:46pm PST.

Can you please provide some insights on what exact request you're making and what responses do you see? Can you please PM to me all this information?

[aarondcoleman]

We're hitting:

https://api.fitbit.com/oauth2/token

Here's the most recent (2 mins go) CF-Ray: 

3bd4dd8b7b7d51b8-SJC

[aarondcoleman]

These 500's increased in frequency substantially overnight. Anyone else seeing this besides us?