Strava 'rate limit exceeded' when trying to connect account

Hi all, we have an update of resolution for this bug: 

We've worked with Strava to identify the problem where your Zap(s) would get a 429 API limit error at the end of the day (UTC time). Strava has agreed to increase our API limits, but they have a ceiling on this limit that, given user growth, we are worried we might hit in the not so distant future.

In order to make sure we do not hit those limits again, we are also limiting our two triggers, New Athlete Activity and New or Updated Club Activity to run every 15 minutes. They will still trigger on all-new activities, just at a longer polling interval.

We hope this won't be forever. We have work going on to implement Strava's specific webhook implementation, which would enable us to offer the Athlete Activity trigger as "instant" and give us much more room in terms of API limits. We don't have an ETA on this work, but we'll make sure you are notified when it ships.

Hi,

Please count me as impacted by the Strava rate limit as well. Thanks. 

this is my user: https://www.strava.com/athletes/34745140

Hi there @mahdikia - You’ve been added to this impacted user report. Thanks!

@steph.n 

Dear Steph,

Thank you very much.