If you pause an activity, then after a certain time the activity is "stopped and saved". I was wondering if it is possible to set this default to "resume later". I don't understand why someone decides to make "stop and save" a default anyways. In case of a "resume later" you can always do a "resume, stop and save". Once stopped you cannot continue the activity. Wonder what your opinion is on this.
Thanks for replying.
Once on a long ride I paused the activity during a lunch break. When I wanted to resume, the activity was stopped and saved. There went my 200 mile record in one go 
Anyways, I thought…
There went my 200 mile record in one go
Assuming you still have the two separate files you an join them using FitFileTools.
"Resume later" will cause incremented elapsed time in activity and GPS position jumps when resuming, which will mess up your metrics...
Thanks for replying.
Once on a long ride I paused the activity during a lunch break. When I wanted to resume, the activity was stopped and saved. There went my 200 mile record in one go
Anyways, I thought why doesn't it use the "resume later" as a default. If you forget to save your activity, you can always return to the activity and still save it, whereas the other way around is not possible. That is, you cannot open a saved activity to resume it.
Of course this can all be avoided by selecting resume later yourself when going for a longer break. I was just wondering what the rational was to choose "stop and save" over "resume later".
