RECORDING

Write “not recorded” when the file is missing

Some sessions will not have a file. The battery died, the permission was off, the Watch never transferred, or you simply did not start a recording. The log still has a job: spot, setup, and the sentence “not recorded.” Filling in a route from memory makes a later reader think a device captured it. FoilBear’s recording guide tells you what the devices can keep. This page is the day they did not.

Say which piece is missing

No phone track, no Watch file, or neither. Those are different gaps. The waiting-to-upload guide is for a file that exists and has not left the phone. Do not use “not recorded” for a file you still have.

Permissions live in iOS Settings and in the Health app, as Support describes. A denied permission can be restored without reinstalling. Fixing it does not invent yesterday’s track.

What you may still write

The launch name, the setup, the wind and tide in your own words, and whether you came in early. Those are observations. They are not a distance and not a line on a map.

If you want a number, it has to be one you measured some other honest way, and you say how. Otherwise leave the number out.

Do not repair the story later

A file that arrives tomorrow gets attached as the file. It does not need you to have predicted it in prose.

A file that never arrives stays “not recorded.” Do not let the note drift into a specific route over the next week.

Questions

Is a session without a track worth logging?

Yes. The setup and the spot are still how you learn the launch. A blank day teaches you less than an honest short note.

Should I delete a ride whose track looks empty?

Keep it and mark what is missing. Deleting the session to tidy the list removes the note that the device failed. Support can look at a ride you still have.