How the auto-matcher works, when to override it manually, and what locking means.
A planned workout lives on the calendar. A recorded activity is what the athlete actually uploaded (a FIT, TCX, or GPX file). Matching ties the two together so you get the full comparison: plan-vs-actual, the compliance colour on the calendar pill, the Session analysis and the Similar sessions trend on the workout detail page. (An unmatched upload still shows its own activity analysis — matching adds the vs-plan layer.)
When an athlete uploads an Activity, Grepiac runs the auto-matcher:
match_locked
set (user explicitly decided).completed.The auto-matcher never overrides a manual decision and never matches across dates.
Common failure cases:
From the workout detail page (/athlete/<pid>/workout/<id>/):
When you manually match or unmatch, the workout gets
match_locked=True. This tells the auto-matcher to leave
it alone. If you later want auto-match to consider it
again, edit the workout from admin and clear the flag.
The system deliberately does not match a Tuesday Activity to a Wednesday planned workout. The risks (matching the wrong day, getting taper or recovery decisions wrong) are larger than the convenience. The fix is to drag the planned workout to the correct date first.
See also: Calendar overview, Drag and drop in the calendar, Workout notes (three kinds).
Still stuck? Ask us a question and we'll write up an answer.
Ask a question