Garmin Connect Not Recording Exercise Time Correctly

Which of the time values are you looking at? There are three of them:

• Elapsed Time: Includes all time from the initial starting of the timer to when the activity is saved.

• Moving Time: Includes only the time you were moving.

• Time/Timer: Includes time moving and time not moving as long as the timer was running (if Auto Pause is turned on this will prevent time not moving from being included in this total).

Strava often uses a different time than Connect, in the header. Connect uses the 3rd option listed above (at least at native activities recorded by Garmin devices). Though Connect reports all three times, on the detailed Stats tab. Have a look at it, and see whether you have the longer time there too.

Post screenshot of the activity stats page in Garmin Connect which shows all three times and scroll down in Strava and screenshot the page with moving and elapsed time. Then we might be able to understand why it is different.

But why should the moving and elapsed times be different?

It's not being recorded on the Garmin device: it's recorded in the ROUVY app as one ride from start to finish and then shared to Strava and ROUVY.

Looking at the blatantly incorrect Connect data for the last short ride, it shows a now-corrected Total Time of 21:12.  On the stats tab, it shows Total Time 21:12 (corrected by me), Moving Time of 11:29 (which clearly cannot be right) and Elapsed Time of 21:13.

Strava shows Moving Time of 21:12 and Elapsed Time of 21:12.

Then it seems like the timer was considered to be stopped for about 10 minutes. Elapsed time is the time from when you pressed start until you saved the activity.

What does the speed chart in Garmin Connect look like?

Constant (but variable) for the full period.

Hey, I have exactly the same issue, from what I see, it started to reproduce recently. 

Today I have:

interesting part is plots showing correct data with correct timing, while Time, Moving Time, Elapsed Time displayed in Garmin Connect are wrong.

My wife's having the same issues.

Today was even more bizarre: the main ride was imported correctly, but both the warmup and cool down rides were incorrectly timed.

If you post the FIT file of the activity, perhaps we can spot where the problem comes from.