Looks good to me. Thanks, @JamesChevalier!
Hmm, something changed. I wasn’t out logged in ,but citystrides asked to reconnect. All my data is gone now? So now i wait to resync everything again? I already see my most recent run from yesterday, so that’s promising.
update: more runs are coming in! All streets are in progress, but i guess that is another job that calculates those, to get them on done. Seems like i have to add my shoes again and determine which cities i am running.
update 2: All is looking good! cities again checked, my newest run from this morning is directly synchronised. So now flag all those churches, powerplants, production locations on done again and we’re good!
James, my run of July 28 is not appearing at all.
Usually it takes 1 day or so, but now it’s not happening at all?
I am using Runkeeper.
Thank you, Marco.
1 Like
I have not seen any runkeeper activities synced since July 24. I figured there was just a backlog.
1 Like
Yup, same here. I’m using Runkeeper and July 24th was the last day any activities appeared. I’ve done a couple runs since.
1 Like
Same thing is happening. When you manually syncd my account the activities showed up but nothing since has come through. I don’t know how you are keeping up on all of this. We need to give you more money.
I’m looking into this issue, but I have no idea why it’s happening yet.
I was able to manually copy/paste the exact code that’s run in my worker server to get it running interactively for @creubank … all the activities were synchronized.
So there’s something about my worker server’s environment that’s causing this to fail for some reason.
It does coincide with my recent effort of putting my sidekiq processes into Docker. So it’s probably something around that.
Update1: I was finally able to debug this effectively & it looks like Runkeeper has drastically changed their API rate limits. I’m now trying to work around this error:
Rate-limit exceeded. Rate limit is 5 calls per minute per user
Update2: I’ve temporarily configured the sync code to just do what it can with the 5 calls/minute limit. This means that it’ll only be able to sync in 5 activities per day (potentially fine for existing users, terrible for new users). I will need to revisit this process so that it keeps a longer-running sync going, bringing in 5 activities/minute until it’s finished. This will require a little rework of my job system, so that a few of these jobs don’t cause a huge backlog of other faster-running jobs.
1 Like
James, as always your work is much appreciated. I suggest you do something like tapiirik does: auto sync (or allow manual sync) to users who sign up for monthly payment … you set the rate. Others get synced weekly.
CityStrides has grown to be too much for one person to handle using the free model. If you get enough paying subscribers, you can can hire an offshore resource to provide support.
3 Likes
None of my runs since the 24th are showing either. I’m using runkeeper
1 Like
I would for sure pay to get my “sync” button back. I was happy to give tapiirik my money
1 Like
I’s also like to have this portion of control back, possibly for paying users only?
My last 2 runs do not appear in citystrides (July 27 and July 30). I use runkeeper. It went well for a long time but last week it failed. (Lucia - CityStrides).
Thanks James - I’m in the same situation, no updates since the 25th. Hope you get it figured out!
There are two ongoing sync issues that relate to this ‘deleted activity’ issue.
- For Strava members: New activities are automatically alerted to me - I no longer poll Strava to sync activities, instead Strava alerts me when you save a new activity (there are no ‘update’ alerts yet). There is a problem here where private activities are not triggering the alert to me. I am working with Strava support on this now (it’s entirely possible that the problem is on my side).
- For Runkeeper members: They recently changed their API to drastically reduce the number of calls that I can make to them. Luckily, it’s a per-user limit, so it should not affect how CityStrides grows. I already have a fix that I believe should sort this out, and I hope to get this released soon. The main drawback here is that Runkeeper syncing is going to be incredibly painfully ridiculously slow (it looks like I will only be able to sync at a rate of 5 activities per minute). There is nothing I can do about that, though.
I’ll update again as I finally resolve these issues. Hang in there, everyone!
Thanks James, it’s appreciated! I am happy that I’m not paying for Runkeeper, this won’t boost their popularity (well, not with for me anyway ;-))
I was having trouble synching my private runs from Strava but through a little trial and error discovered that this was related to the Movescount application I use with my Suunto watch. When I first download my runs to Movescount I had the default set to private so this was also being synched with Strava resulting in none of my runs being synched with CityStrides. I changed the privacy setting in Movescount to Public and now all of my runs synch from Movescount to Strava to CityStrides almost immediately. Just passing this along in case anyone else has a Suunto watch.
That’s helpful info! Nobody should have to make their activities public just to use CityStrides, though. I’m hopeful that my work will result in private activities being just as useable as public activities.
I have the updated code in place, as of last night. By midnight Eastern Time tonight, all Runkeeper users should be fully synchronized… I’ll need to know after that if some people still aren’t seeing al of their activities.
In my quick tests, I did see some skipping. It was a small amount, and it seemed more worthwhile to get the changes out to everyone then optimize it to 100%.
Here we go!
Any headway on strava? My account hasn’t had any syncing since early June other than the time you manulally syncd it
No luck with my runkeeper account - last activity is still July 25.