Yes, but by then it's fucked my Running Estimated Best Efforts. Even if I change the activity type to "Ride" before hitting save.
Premium member, support issue raised. "Sounds similar to an existing bug we're trying to fix" and case closed. Not fixed yet (over a month since I first raised it).
Support also suggested a number of stupid workarounds.
Have you tried changing the activity type to "Ride" within 5 minutes of uploading it? Of course, didn't help.
Have you tried marking it as private, changing the activity type to "Ride", saving it, then unmarking it as private? Yes, still didn't help.
Their problem is that uploading a file kicks off a whole load of automation in the back end before you even get a chance to change the activity type, but by considering it a run it flags it internally as being too fast and blocks the estimated best effort calculations. And then subsequently changing the activity type (no matter how quickly or slowly) doesn't undo what it's flagged as bad.
Even now, since uploading a recent 10k run I've still only got Estimated Best Efforts for 1k and 1 mile.
I can manually raise a ticket to fix it but that gets boring, I just wrote my own scripts to parse the .tcx files and calculate it myself.
Yes, but by then it's fucked my Running Estimated Best Efforts. Even if I change the activity type to "Ride" before hitting save.
Premium member, support issue raised. "Sounds similar to an existing bug we're trying to fix" and case closed. Not fixed yet (over a month since I first raised it).
Support also suggested a number of stupid workarounds.
Have you tried changing the activity type to "Ride" within 5 minutes of uploading it? Of course, didn't help.
Have you tried marking it as private, changing the activity type to "Ride", saving it, then unmarking it as private? Yes, still didn't help.
Their problem is that uploading a file kicks off a whole load of automation in the back end before you even get a chance to change the activity type, but by considering it a run it flags it internally as being too fast and blocks the estimated best effort calculations. And then subsequently changing the activity type (no matter how quickly or slowly) doesn't undo what it's flagged as bad.
Even now, since uploading a recent 10k run I've still only got Estimated Best Efforts for 1k and 1 mile.
I can manually raise a ticket to fix it but that gets boring, I just wrote my own scripts to parse the .tcx files and calculate it myself.
Useless shite.