Hey! Thanks for the report.

I took a look at this one and the most likely explanation is that the workout was viewed before it was finished being logged. This session was a standalone workout, not a scheduled calendar session, and the athlete logged it progressively over time. Early in the session, only the first exercise had been saved, so checking the calendar at that point could make it look like the workout only had a single exercise. Later, once the rest of the workout was finished and saved, the full session appeared in history as expected.

At this point I’m not seeing evidence of a persistent data-loss issue or an outdated calendar cache version for this user. This looks most consistent with the session being viewed while it was still in progress.

If this happens again and you're able to identify it is as a mismatch on the screens when displaying a confirmed finished session, don't hesitate to let me know