Showing results for 
Search instead for 
Did you mean: 
Status: Archived

A friend and I descended Latigo Cyn, caught our breath and had some nutrition at the bottom, then headed up. Apparently somewhere at the bottom, we triggered the segment start even though we were not moving. First off, that's bad segment design, should always start a tiny bit up the climb to avoid situations like these. But can't Strava deal with this intelligently by recognizing that there was zero progress at the segment start, and not begin the real timer until there is progress? Regards, Paul

Status changed to: Gathering Kudos
Moderator Moderator

Thanks for submitting your idea. It has been reviewed by our moderation team and is now open to voting.

STRAVA | Community Hub Team

Status changed to: Archived
Moderator Moderator

Hello. We wanted to let you know that your idea submission from November of 2022 will be archived. While this idea is interesting, we don’t have any immediate plans to implement this and currently aren’t able to prioritize this idea.

Please note that your feedback is valuable to Strava. As stated in our Community Idea Guidelines, we receive many idea submissions each week, and realistically, there may be various reasons that prevent us from including an idea on our Product Roadmap.  

We want to thank you for taking the time to submit your idea and we look forward to your continued contributions to the Strava Community.  

Jane (she/her)
STRAVA | Community Hub Team