Distance issues walking ok biking totally wrong

Do you use a bike speed sensor?
Did you look at the speed during the activity? Was it ok?

Been thinking a bit
could it be that the problem lies in the cadance/speed meter?
It would be strange because it gives the proper readings on runkeeper and it worked on the vivoactive HR flawlessly.

I'll try a ride this Saturday without the accessory connected. Which would be a bummer in all honesty
On the other hand if it doesn't calculate vo2max anyway for cycling in fine using only the edge

You timed while I was typing :)
on runkeeper the speed is correct and I don't use runkeeper it takes the info from garmin connect

If runkeeper would also show errors I understand the weird thing is that runkeeper had cadance speed and distance and heart rate spot on

When looking closer to the info inside Garmin connect it's indeed the speed that is in error ciq.forums.garmin.com/.../1256481.jpg

Runkeeper probably takes speed and distance from the GPS track and that's why you have speed and distance in runkeeper but not in garmin connect.

I have seen issues with the speed/cadence sensor connectivity. I?ll see zero speed and cadence values while my bike computer shows normal ones. I haven?t had time to look into it.

It's indeed my cadance and speed sensor. When I disabled those it was ok for distance. Elevation is weird btw as you can see in the screenshot. Trust me I did not have so much elevation lol.
i do think it's weird it won't work right with my cadence/speed meter. The HR did and the edge 820 does.

Hope they fix that ciq.forums.garmin.com/.../1257232.jpg

I'm not sure if the VA3 is having difficulties with detecting sensors, or if it's just my device. I have 3 heartrate straps,1 ANT+ and 2 BLE. My watch works flawlessly with my ANT+ strap, but can't detect either BLE strap. I also paired Garmin speed and cadence sensors for my bike. The first time I wanted to go for a ride, my watch was stuck "searching" for both sensors. It had been a while since I changed those batteries, so I gave that a try. Same issue. I grabbed my FR235 and both sensors connected within seconds. I had to prop up my rear tire off the ground, pedal as fast as I could with one hand as I placed the watch as close as possible to the sensors with the other hand. I finally got them connected and they worked fine during my ride. Reading what other issues people are having with their sensors makes me hope this is corrected in a FW update and not something specific with my watch.

Connecting was no problem at all
the scosche connected right away and also my wahoo cadance/speed connected right away

When using it it went wrong
So I would try another unit in your case.