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

This happens from time to time and usually isn't a bug in the app – it comes down to the data we receive.

What Trait gets from your watch: Watches and services essentially only send raw data – GPS coordinates and a timestamp for each data point. Trait calculates pace, kilometer splits and much more from that itself. There are a few typical pitfalls along the way:

• Pauses often aren't included. If you stop briefly during a run without your watch registering it as a pause, there's a big gap 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 splits.
• Data quality varies a lot: sometimes there are two seconds between data points, sometimes 0.2 seconds, and every now and then points are missing entirely.

Trait does its best to interpret this data. Still, the occasional workout may end up with implausible values.

Special case – treadmill: If you recorded a treadmill run in your watch's outdoor mode, it measures almost no distance via GPS (e.g. 100 m instead of 10 km) – that's down to the recording, not to Trait. Even in indoor mode, the watch's estimated values are often inaccurate.

What you can do: Distance and duration can be corrected afterwards for all running activities. Just tap the run in the Calendar and choose edit. That's also the way to go after a treadmill run if the values don't look right.

By the way, a personal best wrongly detected from data like this doesn't affect your training paces. Unfortunately, the personal bests list itself can't currently be corrected. If what's actually bothering you is an off forecast, you can enter a real current performance: Stats → tap Feelgood pace → Forecasts, then look for the fine print below: "These estimates are wrong? …".