I have had my FR230 for just over a week now. I have not recorded to many activities yet (~4). After my activity, I enabled auto pause and set it to "when stopped". I had one pause on the route for a few minutes. When I resumed my workout, I noticed that the timer did not resume until I has moved a few hundred yards at a pretty brisk pace before it resumed. I suspect that this is because I was at a walking pace and not running. This problem became more apparent when I was walking a dog and my watch paused when I stopped to lock the door. I was able to walk at a leisurely pace with the dog and the auto resume never kicked in. I was able to walk over .25 miles before I just turned it off and relied on activity tracking. My wife had a similar activity which Auto paused was enabled and it recorded a .5 mile walk when I know the route she took is over 1 mile long.
Based on my experience with my Edge products, I figured that "when stopped" would be the most sensitive to restarting at any pace, especially walking. On my past edge products (edge 305, 705, and 810), the when stopped unit would resume as soon as the unit detected any speed, resulting in many resume/pauses when stopped for a break. I learned that for riding a 3mph threshold is fine for cycling, but not good when walking with my wife. It so happens that the default for custom pace is ~3mph (20min/mile), which makes me wonder what the threshold is for "When Stopped". As an experiment I have set the custom pause pace to 59min/mile to see if that makes it more responsive.
Has anyone figured out what minimum pace is needed to resume the activity timer when auto pause is set to "When Stopped"?