You uploaded one file, yet several separate workout parts appear in the log. At other times, the problem is a cycling section and changing time appearing as running in your weekly total. File count is a misleading clue here. One FIT activity can contain several distinct sessions.
A Session is not the same as a lap, one workout-instruction step or a manual pause. A warm-up does not automatically become a separate session because you ran at another pace either. We follow the difference through an original fictional run–bike–run example, then examine how to check totals by sport. The aim is for the log to tell the same story the recording actually contains.
Activity is the whole event; Session can be a distinct part
The official Garmin FIT Activity description explains that an activity file can contain one or more Session messages. In multisport activities, individual parts and transitions can appear as separate Sessions. One storage unit can therefore bring together several different sporting parts. The whole activity and one of its sessions need not have the same data.
In an original example, an athlete runs, changes, cycles, changes again and runs again. If the recorder describes five sessions, the file remains the history of one connected event. Sessions can be interpreted with separate starts, durations and sport labels. This is not five independent uploads but structure within one file.
A simple importer therefore needs to do more than read the first sport label and assign the whole file to it. The first part may be running while the greatest later distance is cycling. Correct grouping is necessary for sport-specific totals. Filename, title or first map point does not replace reviewing the internal sessions.
A warm-up usually does not mean a separate sport
Warm-up, work and cool-down describe workout structure. They can occur within one running session, for example as laps or sections linked to instructions. Everyday use of “separate part” is therefore insufficient to assume a Session message. Actual file structure and recorder operation determine storage.
In our original simple run, ten minutes warm-up, twenty minutes steady running and eight minutes cool-down all use the same running mode. The recording can be one Session containing several Laps or other section markers. A pace difference alone does not create a new sport session. There is no need to create three separate runs merely because the task had three functions.
It differs if the user actually started and saved separate activities or a multisport mode created separate sessions. The result can then differ from the preceding example. Correct checking always begins with how the process was recorded. Coaching-plan names and technical file units may be linked, but a one-to-one relationship is not compulsory.
Our five-part example: 27 kilometres is not 27 kilometres of running
Our deliberately simple fictional series starts with four kilometres of running in twenty-four minutes. A three-minute transition follows, then twenty kilometres cycling in fifty minutes, another two-minute transition and finally three kilometres running in eighteen minutes. The whole event lasts ninety-seven minutes, and distances in the two moving sports total twenty-seven kilometres. We assign no separate distance to transitions in this example.
Running is only seven kilometres and forty-two minutes, however. Cycling is twenty kilometres and fifty minutes; transitions total five minutes. Calling all twenty-seven kilometres running overstates weekly running mileage by twenty kilometres. A sum can be mathematically correct while its sport label is wrong. The problem arises in assigning meaning, not adding distance.
Total time divided by total distance is approximately 3:35.6 minutes per kilometre. Displaying it as average running pace misleads because it includes cycling and transitions. The two actual runs together average six minutes per kilometre. No improvement in running technique explains the difference: different sporting content entered the numerator and denominator.
Enlarge imageTransition time can be preserved separately
A change between sports is not automatically running training. It can include changing equipment, moving between places or waiting, while the system still records it within the event. Preserving the transition is useful because it belongs to the whole story. Preservation does not require assigning every minute to a running or cycling section.
In our original example, adding five transition minutes to forty-two running minutes gives forty-seven. Dividing by seven kilometres yields about 6:42.9 minutes per kilometre. Distance is now correct for running, but time uses a different definition. This shows that time type and transition handling matter alongside filtering by sport.
The whole event can still remain ninety-seven minutes. Total time and sport-specific times do not compete; they answer different questions. One says how long the event lasted, another how much belonged to running and cycling. Appropriate labels make the displayed number understandable.
Session, Lap and Record: differently sized units
Session summarises one session, Lap can describe a lap or section inside it and Record can carry detail at a timestamp. The documented structure can have several laps and many timestamps within one session. A manual lap marker is therefore not the same operation as changing sport. Detailed analysis requires knowing which level the programme uses.
In our run–bike example, the first run has four automatic kilometre laps and the second three. Together these may mean seven running laps while running appears in two Sessions. The cycling session can have its own laps. Simply counting laps does not reveal session count, and session count does not equal interval count.
The FIT decoding guide shows grouping messages into Sessions by time range and also discusses lap indices where available. Not every manufacturer supplies every index. Processors therefore need to use available valid fields. Display order alone does not justify assuming a complete relationship system.
Sport and subsport give more precise clues than a title
A title such as “Tuesday training” says nothing about which file section is running. Session sport and subsport labels can provide technical clues for separation. A user’s title can be a separate free-text note. Do not swap these roles: an evocative title is not a suitable automatic sport classifier.
In an original archive, the complete event is titled “Sunday combined”, with sport and start time separately recorded beside each session. A running summary can then select both runs without interpreting the title’s language. Another log may show the whole event on one card. Card count still does not tell you whether background sport-specific calculation is correct.
If recording began in the wrong sport mode, a formal label does not solve everything. Document the difference between actual movement and recording mode. Software may start from the file’s claim and need not infer the sport afresh from every route. Correct recording, an accurate note and processing together create an interpretable log.
Reading the whole file can avoid overvaluing its first part
The decoding guide explains that summary messages can appear at the end. Examining only the first few rows or first sport label may therefore be insufficient to interpret structure. A later Session may add another part. Gather valid sessions from the whole activity before drawing a final conclusion.
In an original checking example, a subtotal appears on the watch after the first run, but recording continues with cycling. If an external processor treats the whole event as finished after that part, later data may be absent from the view. Another possible fault retains it but groups it under the first running label. Missing data and merging are different problems requiring different checks.
The FIT protocol description treats defined file and message definitions, types and timestamps separately. It provides a technical basis for structured processing but does not replace the receiving app’s sport logic. A valid file and an appropriately chosen log summary are separate checks. Success in one does not automatically imply the other.
Enlarge imageCross-check each session before weekly totals
In a brief personal table, give every Session a row: start, sport, time, distance and classification shown in the app. Our five-part example immediately reveals two runs, two transitions and cycling. Running distance and time can then be totalled separately. You do not need to inspect every Record manually to identify a basic sport-classification error.
Use matching time concepts in the cross-check. Comparing sessions’ elapsed time with the whole event’s moving time can differ, especially with pauses and transitions. Align labels and duration definitions first. Only then look for missing minutes or double-counted sections. A discrepancy can be a legitimate difference in definitions too.
Workout count remains a separate decision. A coaching log may record a combined occasion as one event but two running blocks. That works if its rule is consistent and visible. “Three runs this week” requires knowing whether two short running parts within one occasion count as one or two. Distance and number of occasions are different measures.
Do not lose the original connection after splitting
If a receiving log creates separate activities from sessions, retain their connection to the common event. An original archive can add a shared group marker and source filename beside the parts. The cycling preceding the second run then remains visible later. A section stays independently analysable without losing its context.
Before deleting or renaming a transition, consider what question the recording serves. If totalling only running distance, excluding the transition from the filter may be enough; it need not be removed from the original. Keeping the source unchanged allows later analysis from another perspective. A simpler view and complete archive can coexist.
One FIT file can therefore carry multiple sessions, but not every workout part is a separate Session. Checking sport labels, session boundaries and time types together shows what belongs in weekly running totals. Internal structure matters more than file count. The log then preserves the combined event while its running numbers genuinely describe running.
Sources
- Garmin FIT Activity: multiple sessions, sport sections and transitions.
- Garmin FIT decoding: laps and records grouped by session.
- Garmin FIT protocol: message definitions and timestamps.
How Futószív articles are prepared: our editorial guidelines.


