We want every participant reauthorized before the Fitbit Web API shuts off, but we know that won't always happen. Here's what to expect if someone misses the deadline.
Past data is preserved
Data that has already synced to Fitabase is not lost or affected. We're swapping one data connection for another, and nothing that's already in Fitabase goes away.
New data pauses
Until a participant reauthorizes, Fitabase can't pull new data for them. For the time being, you won't have real-time data or compliance monitoring for that participant.
Fitabase backfills the gap once they reconnect
When a participant reauthorizes, even weeks after the cutoff, Fitabase automatically goes back and fills in the data from the time they were disconnected.
Important:
Backfilling only works for data that reached Google. The participant needs to keep syncing their device to the Google Health app as usual in the meantime. That part isn't changing.
Expect brief sync delays during the transition
As Google moves traffic over to the Google Health API, there may be short "brown-outs" when syncing is delayed. Data synced during a brown-out still comes through. It just may take longer to show up in Fitabase.
Tip:
The reconnect option stays available after the cutoff, so a participant who misses the deadline can still reauthorize. Keep following up with anyone on the Requires reauthorization tab until they're reconnected.