Oh, that would be unfortunate…
Thanks, I’ll give it to tomorrow.
They tend to update daily at about 02:30hrs. So it may have missed today.
Good job I have 39 days in the bank to spare as well ahead of target.
1 Like
I have an active time goal set up - Garmin is back up, at least partly, but my time still hasn’t updated on Beeminder for today - I’m risking defaulting on this goal if it doesn’t.
1 Like
All the functions on my Connect dashboard seem to be back to normal, but I still have the “server maintenance” popup. The link in @apolyton’s post still says third-party sync is delayed, too, so my guess is that we just have to be patient a few days longer.
1 Like
Just a single data point, my Garmin -> Strava -> Beeminder automations worked fine (e.g. sync in about an hour after workout) yesterday
2 Likes
My Beeminder goal syncs straight to garmin… Maybe that sync is still delayed? Whereas garmin -> Strava has gotten priority at garmin? @dreev, any insight on this?
1 Like
Yeah, it looks like the Garmin Connect stuff is back in my own dashboard, but there’s definitely still something weird with the API. I don’t have any guesses as to why API service would restore separately from Connect service (I was under the impression that we were getting our data from the same place Connect sends it), but I may have to follow up with them, and I imagine they’re super swamped…
So, my Connect dashboard is back and has data in the blackout period, but when I make a request to their rest API from in that same period it’s just returning blank stares. Possibly there could be an authentication issue? Has anyone tried re-authenticating Beeminder to their Garmin data? They’re not giving an ‘unauthorized’ error, but that’s probably worth a try.
We don’t automatically sync the previous week of data with Garmin, so once the api is actually serving us data again, I’ll have to queue up a special job to fetch everyone’s data back to the 22nd.
1 Like
Thanks for the update, @bee! (see especially Bee’s edit to her answer for those seeing these via email) To clarify, our new somewhat aspirational standard for autodata is that it always automatically keeps the last 7 days in sync with the autodata source. That’s not the case yet for Garmin but we’re committing to re-syncing your data back to when Garmin’s outage started. As soon as Garmin’s API is fully operational, that is.
1 Like
Are you getting data for days after that period? I’m not getting anything added to BM since the problem started on July 22.
I just tried, but… Beeminder ignored it? I de-authorized Beeminder at my Garmin Connect account, but when I refreshed my BM goal it didn’t give a peep. I had expected BM to complain that it no longer had access and to prompt me to re-enter. So looks like now my BM goal is not even connected to Garmin, but it still tells me everything’s business as usual.
So the one thing is obviously that I need to get BM reconnected to my Garmin account, but the other thing is that maybe this is some kind of clue to why all the blank stares from the Garmin API…
EDIT: BM just prompted me now. I re-authorized, and still not getting any post-July 22 data from Garmin.
2 Likes
Thanks for being the intrepid tester with that, Grayson! I’ve checked in on the Garmin Developer portal and the info they’ve got up seems a bit contradictory – their latest blog post (from July 27) says “backfil data isn’t available yet, but activity summaries are going out as normal”, which sounds like we should be getting pushes with new data at this point, which does not seem to be the case. But then, in another spot I found a detailed listing of API status that looks like most things are still down:
Anyhow, it’s frustrating that they’re not being more transparent about the state of things over there! Seems they have plenty of employees to put someone on just like, updating the blog regularly to tell us all what they’re working on. I posted on their developer forum asking for an update, and now I think we just wait 
2 Likes
Oh, actually, that would be a thing to look at, among the folks who’ve commented in this thread already, what different things are we using Garmin for? Is anyone tracking activities, e.g. run mileage or something like that? And is the status of those goals any different from the “dailies” (i.e. steps) goals? or sleep?
3 Likes
I’m tracking activity minutes, and that is syncing to their main server through the app, but doesn’t appear to be piped back down to the beeminder universe via their API. My garmin goal hasn’t had an update since they went down…
3 Likes
Ok, I looked a little further and we are indeed getting data sent over for people tracking activities – that includes total mileage, and duration of activities, but doesn’t include the “active time” metric. The active time metric gets info from the same place as we get step counts, so that is still down.
4 Likes
I’m tracking steps from my Vivoactive 3, direct from Garmin, not going through Strava.
My activities have synced to Garmin Connect and Strava now, but my Beeminder goal hasn’t been updated since the 23rd. Should I ping support?
3 Likes
They’re already aware of the issue, so I think you only need to contact them if your Garmin goal derails as a result of the outage. Once Garmin is fully back in order, @bee will take care of getting everyone’s past data back filled, as I understand it.
6 Likes
No new info from Garmin so far this Monday. Just a generic reply saying “thanks for being patient with us!”. Sleep & dailies apis are still down.
And yes, I confirm Grayson’s summary above. Once Garmin’s fully back I’ll make sure that all the back data is filled in. In the meantime there’s naught to do but wait. If you do derail in the interim, please reply to the legit check so we can cancel the charges!
Thanks
6 Likes
update for 08/04: no news :sadface:
Yes, we are still recovering from outage and some services are still down. We apologize for the inconvenience. Our team working 24/7 on brinning all services back.
Thanks,
Garmin Health API Support
4 Likes
I heard on a podcast that Garmin got hit with a ransomware attack.
They did, and they “acquired” the decryption key!
Oof, that’s too bad they had to do that.