When I am crossing roads, I do not want the waiting time being recorded in my runs. Depending on the traffic this can be from seconds to 1-2 minutes.
Well, on my Garmins, I had one button which was "Start/Stop". Did work perfect, never had to think where it is or if it had paused/resumed as both was clear from the reaction of the watch. It pinged and vibrated and the screen got a red surrounding on pause and a green (disappearing) surrounding on resume.
Ah I remember that before my 235 died!
What might work for you if you dont want to turn autopause on is to configure double or triple tap to be pause/resume?
What I do which is vaguely similar is config double tap as “next interval”. I have an interval plan which is just 1000x repeats of ”run” and “rest”...
Its not quite the same, as during my run, I only get to see the time and distance of the current run interval, rather than the total of all my run time with all the rest intervals removed. But it works for me as I generally want to see “current interval pace”. This gives a nice breakdown you can click through the interval segments on the phone app and analyse the moving bits individually.
Another advantage of this approach is on the “rest” interval you can build a custom screen which is displaying for example some data from the previous interval such as previous interval pace time and distance, plus maybe your current heart rate or something.
Then I just let Strava do it’s magic with its interpretation of my moving time so I see the overall moving average pace.
Mostly when doing a social group run I just ignore my watch to be honest, but if I decide I want to analyse afterwards, even if I HAVENT use an interval profile and just started a regular open running session, then double tapping to create a new interval still works and it’s usually easy when looking at the analysis for see the intervals I tagged as not moving.
You could use laps instead of intervals, but I find it easier to keep the Autolap ticking away on 1km cycles independent of the manual intervals.