api failures/timeouts 6/22/2015

[CernerWellness]

https://api.fitbit.com/oauth/request_token
https://api.fitbit.com/1/user/26T4JF/devices.json

I am seeing lengthy delays in querying device information or during the registration process for the api.  These are resulting in timeouts in my application.  Steps are coming through but I am unable to get device info.  Is anyone seeing this issue?

[JeremiahFitbit]

Can you give an exact time period? Are you still seeing this problem?

[CernerWellness · Accepted solution]

Issue appears to be resolved.  Seemed environment specific outside of fitbit.  Cycling application services on my side of the app resolved.

[CernerWellness]

Hello Jeremiah

This was first reported yesterday morning (~9am eastern).  It was again reported today at the same time.  The calls that are reporting as timed out are sourced from our  .NET web application.  Cycling the application resolves the error.  My current thought is that the applciation could be caching something on our side.  I can make changes if needed to the config of the app, but would like to know if there were any changes fitbit side that could result in cached application side information from my app to be invalid.

[JeremiahFitbit]

There are many caches in our system, but I don't know how they would affect your application connecting to the Fitbit API. We're not seeing increased response times on our side or connection refusals.