Increased Errors OA2 Token Refresh - InternelServerErrors | Gateway Timeout

[aarondcoleman]

Starting at about 7:30PST and continuing now we are seeing an increase in 500 and timeout errors to the refresh token endpoint of the Fitbit API. Immediate retries once or twice eventually succeed. Also, calls that do suceed appear to take much longer than normal.

Just reporting this as our queue & retry logic is at present smoothing this out on our end. Seems to be increasing in frequency though.

Thanks,

--Aaron

[aarondcoleman · Accepted solution]

Errors stopped and response times returned to sub-second at about 9:30pm PST. Just FYI