Auto-pause doesn't resume

I never have trusted auto-pause to pause and unpause perfectly. Even if it worked well, I still wouldn't use it. I just don't trust any device to figure out for me when I actually truly stopped and started again, it will nearly always be off be a few seconds even in the best case. Worst case is it doesn't recognize stops or starts at all, as you're experiencing.

Best bet is to just use the top-right button.

I use it for running. I target a specific speed during certain types of training. Ideally it's a continuous run, but things happen -- keys fall on the ground, I stop to let packs of coyotes pass (really), pee, etc. These screw up my speed reading.

I have a fenix 6 Pro that is 2 weeks old and auto-pause works well when I walk. Stops and restarts as expected. 

It depends where you are running. If you’re running in situations where the signal is weak sometimes it never recovers, which is why I and others leave it off. If you have a problem with auto-pause when there is nothing in the way to block the GPS signal that’s a different matter.

A little more detail about where you are or what you are doing when the auto pause does not work as you would like would help.

I was running on a relatively flat dirt trail with nothing to obscure the GPS signal, just low brush. I was averaging 9:05/mile or about 6.6 mph. That should have been plenty to make it resume. I was tracking GPS+GLONASS. Later, after reading some comments, I switched to GPS only. It resumed after about 15 seconds. It seems that Garmin is heavily filtering the signals to get rid of the jitter and that filtering makes it very slow to realize that the user is moving.

2187878 said:

It seems that Garmin is heavily filtering the signals to get rid of the jitter and that filtering makes it very slow to realize that the user is moving

Where did you get that information? Garmin does it's post processing after the activity is finished.

Low speed and overhead cover are sufficient for the watch to assume lack of movement. Once lost, if moving and cover is degrading the signal it can take time to resume. In those situations best thing is to stop and give the watch time to relocate. However, best overall is to turn off auto pause and keep the signal even when it is s little degraded.

Dr Phil said:

Garmin does it's post processing after the activity is finished.

Every GPS device uses Kalman filtering or variations on it combining recent points, velocity information (and accelerometer/gyro in the units that have it) to come up with the best estimate for current location. If there's enough tree cover it'll struggle even then. The filtering gets more aggressive with poor view.

To the OP, I find autopause works really well on the bike but I've never thought much of it for running (granted it's better these days than the old Forerunner 301 which would literally pause and restart if you ran under one tree). But your experience sounds pretty poor. What's your autopause setting in the app? "When stopped" or Custom? If custom, what pace do you have there? How does your GPS track look - does it match the trail reasonably well?

I tried auto pause when I did my first hike, realised when I got home it didn't work for slow moving activities and turned it off. Problem solved. Just on of those features that sounds like a good idea, but isn't.

Auto pause works very well, but for walking / hiking it needs to be set to custom and not 'standard' that way you can drop the speed down so that it pauses correctly

For biking, running etc the auto setting work just great