Why are the duration, pace or distance of my imported session wrong?

This happens from time to time – especially with Polar, Garmin and Apple Watch runs – and is usually not a bug in the app, but a matter of the data delivered.

What Trait gets from your watch: At their core, watches and services only deliver raw data – GPS coordinates and timestamps per data point. Trait calculates speed, kilometer splits and much more from that itself. There are some typical pitfalls here:

• Pauses are often not delivered. If you briefly stop along the way without your watch reporting it as a pause, there's a big difference between gross and net time that Trait has to detect on its own. That's why the duration in Trait can differ from the one on your watch.
• GPS jumps can look like a short sprint and lead to unrealistically fast segments.
• Data quality varies a lot: sometimes there are two seconds between data points, sometimes 0.2 seconds, and points are frequently missing altogether.

Trait does its best to interpret this data. Still, there are occasional sessions with implausible values.

What you can do: Distance and duration can be corrected afterwards for all running activities. To do so, tap the run in the calendar and choose edit. This is also the way to go after a treadmill run in your watch's indoor mode if the estimated values don't fit.

By the way, an incorrectly detected personal best doesn't affect your training paces – it can be corrected separately via your personal bests.