This is not really a bug but more of an implementation issue. The power spike detection feature is clipping all my sprints because I have a low FTP. I personally think that FTP has no correlation with sprint power, my 5 second power increases when I train it, not when my FTP increases. The current method of detecting power spikes is not effective.
At the default 20% level, my sprints are getting clipped at 200-400 watts. You could take any untrained person of the street and they would easily be able to hit these numbers in a sprint. In one of my past rides, it requires setting a threshold of 106% to not have any clipping in the sprints.
Finally, I have changed the default power spike threshold to 100%, however it only affects rides in the future. I am not sure how to change it so that all my previous rides which were incorrectly altered are fixed. I can go through one by one, but I don’t know where my sprints are in all my old rides.
It will take a few minutes to re-analyse everything. There is also a little orange marker on activities that have the power spike threshold set (i.e. that have power spikes clipped or that would have had if you hadn’t edited the threshold):
@david I’m also facing a similar issue. I’ve recently started cycling post-surgery so my FPT is very low (~111w) and as a result my sprint attempt in unscheduled workouts is being clipped significantly. in my last activity, it has been clipped substantially.
