Fitabase experienced a minor incident on November 21, 2017, lasting 2d 10h. The incident has been resolved; the full update timeline is below.
Update timeline
- identified Nov 21, 2017, 06:18 AM UTC
We've identified an issue with the Fitbit API where about 1% of profiles are not syncing data from Fitbit. These profiles' OAuth 2.0 tokens fail to refresh, something we do every 1-8 hours. We are working with the Fitbit API Team to resolve this, and they've indicated that a few manual steps on their end should be all that is needed. We'll update when we've completed the re-connection of all profiles.
- resolved Nov 23, 2017, 04:58 PM UTC
Coordinating with the Fitbit API team we re-established all profiles connections and queued up all data pulls for those few profiles spanning the day or two of disconnect each. We will continue to closely monitor for profiles that enter this over the next few days.