Fitbit Sync Delay 6/26/15

editorgrrl
Posts: 7,060 Member
https://myfitnesspal.desk.com/customer/portal/articles/2039583-fitbit-sync-delay
June 26, 2015
Hello everyone,
We are aware of the reports of delays with the Fitbit integration. This may look like a few different things to members, including a delay in sync of exercise and/or food, no sync of exercise and/or food, receiving an adjustment that is low (due to delay in sync), or not receiving an adjustment. Our team is currently investigating the cause and we're hoping some users will see relief from these symptoms as we continue to work through our backlog.
Please note: At this time we do not recommend unlinking and relinking the two programs. This will increase the number of requests on our servers and could further delay the resolution for our members.
Please check back to this article for further updates on the matter.
Best,
MyFitnessPal Staff
0
Replies
-
Not so much a delay, but a cessation of syncing on app is what I'm xping. Is this what they are speaking of. I've been unable to sync from phone app using android, the desktop app is fine.0
-
They mean MFP is having trouble syncing with Fitbit, so your steps and/or adjustment may be wrong. And/or you might not see your aggregate meal data & water in Fitbit.
If you're saying you're having trouble syncing your tracker with Fitbit, that's got nothing to do with MFP.0 -
My steps and exercise are not updating and my phone app when i enter into food diary is not updating on the desktop appp on mfp or fitbit.0
-
My steps are still syncing, but it's taking twice as long as usual to transfer over to mfp0
-
oops I jinxed myself!! Mine hasn't synced for the last 3 hours0
-
Fingers crossed it seems a wee bit better this morning.0
-
MFP posted an update https://myfitnesspal.desk.com/customer/portal/articles/2039583-fitbit-sync-delayJune 28, 2015 6:55pm PST -
Hello, our backlog was worked through yesterday, but we are again seeing the same symptoms as above starting the morning.
We continue to have a backlog and we have alerted our team of the persisting problem. We will continue to update this article.0
This discussion has been closed.