Negative distance step #x of xxx km detected
There are some edge cases where we cannot import activities. Some vendors and apps that record and create activity files also often manage to incorporate time jumps into the files. This means, for example, that at one point in time a distance X is first called and at the next data point one second later the distance is suddenly almost half a kilometer shorter. However, we have decided to reject such activities. The data just doesn't make sense at this point.
Didn't find an answer to your question?
Please let us know if you have wishes or have encountered bugs. We give our best to make Runalyze as good as possible for you. - Therefore we would be interested in your suggestions for improvement. In general most questions, problems and ideas are more appropriate to ask in the forum.