Request Timeouts - anyone else?

[blakjakau]

We are seeing a number of request timeouts during API interactions from our website(s).

These timeouts first started occuring on March 18th 2016.

We have seen these timeouts against multiple API endpoints including

• Token Refresh requests
• Request token exchange
• user/-/activities
• user/-/profile
• subscription delete

These timeouts have occured across multiple apps, processing request from multiple users, and at different times of day.

It's concievable that this may be caused by local network issues, but we've not had any other indicators from our services, or the 3 other APIs our users can link with.

Is anyone else experiencing the same, can fitbit comment on the timeouts?

[JeremiahFitbit]

Timeouts are a thing that can happen, though they should be rare. Retry the requests.

[blakjakau]

Timeouts have been relatively rare (9 occurences in 10 days, over 5 sites and hundreds of users).

Where the timeouts occured during processing, we do gracefully fail and retry on the next job run.

Prior to the 18th, we've not had any timeouts with the Fitbit API, so I just wanted to make sure it's not a systemic problem.