GOTOES Strava Tools Forum

Hi,

I have observed recently that some activities are not appearing on the Garmin to Strava tool.

I have the feeling that it is occuring with “short” activities, like under 10km. As an example, I recorded one day a ride in several parts and only “long” ones were present, while the shorter were missing.

Just in case it helps, today I recorded this one and is not appearing in Gotoes:

https://connect.garmin.com/modern/activity/18106530433

My gotoes user is pedrojsoria@gmail.com

Could you please help me to solve this?

Thanks!!

Pedro

This happens to me too. I didn’t consider it was short activities. I thought it was when two or more activities upload simultaneously to Garmin. Regardless, I have checked the logs and this is on Garmin’s end. Garmin sends the files to GOTOES listener page… only thing is that occasionally Garmin never sends them. Activity send trigger is once - when your file is uploaded, and Garmin does not try again if it fails. GOTOES is therefore completely unaware of the file. Best thing to do would be to contact Garmin and get them to improve their API. You will notice that the same thing happens occasionally with all other apps that Garmin ports to (including Strava). Sorry that I cannot fix this one.

Thanks a lot for your nice answer. I’ll contact Garmin then.

Best Regards,

Pedro

I've been researching this and looking into my logs. There are so many users registered on my site now that I'm getting upwards of 5 pings a minute from the Garmin API. Since there can be big files, I think that my server is denying rapid-fire requests thinking they are DoS attacks. As such, I implemented a new strategy to drastically minimize the pings; All free users will get deregistered. This will dramatically lessen the amount of traffic from Garmin. Also, I plan to implement an automatic de-reg for users who haven't used the Garmin->GOTOES->Strava feature in x months. I think a lot of people connect their Garmin Accounts to GOTOES without knowing why they are doing it.

Thanks a lot for following up and solving this issue

Best Regards,

Pedro

Thanks, Pedro.

I cannot promise that it is resolved. The issue is that the server has rate-limiting security and Garmin doesn't have a retry option when it get a "valid" reply (the valid reply is actually a "429 error, or 'Too Many Requests'" error. Sadly, the Garmin API will not retry if it encounters this. Ideally, it would try again if it does not get a valid "200 Success" reply. But I can't control Garmin! Regardless, by dramatically getting rid of users, there should be a LOT less pinging of my site by July. This means that Garmin's API should be getting more 200's and less 429's ! Thanks for your patience.