Yes, I’ve had this happen too. I thought maybe because I was dual-recording (Lezyne head unit connects to sensors via Ant+ & has no issues), but this is a new problem that only started happening last week, so I thought I’d give it a few rides to check. Also there are people dual-recording between TR & Zwift so I don’t think it’s that. I’m using a Samsung phone connecting to Assioma Duo, & Trek/Bontrager HRM & speed/cadence sensors.
For me it disconnects from all sensors simultaneously at a randomly-selected time (as though someone grabbed the phone & either ran away with it or turned off BT), no error messages are thrown up by the app. In my case it is able to reconnect but doesn’t do so automatically; I have to go into the device settings in the bottom right corner & show all devices, which of course pauses the workout.
A screenshot from when I was doing James last week:
About halfway through the work period it disconnected from all sensors. The green line continues, indicating that the app knew that the workout was still in progress & hadn’t been skipped etc, but had just stopped receiving data. I didn’t know this because I’d turned the phone screen off about 20 minutes into the work interval because I was dripping sweat onto it which was registering touches. Turning the screen off has also not been a problem before, & the app continued to record data for about another 20 minutes before disconnecting.
Because I was dual-recording, I was able to exit the workout without saving, & instead let it import the upload of the head unit data from Strava, then associate. (It was 85’ @ 74%. Easy for the brain, if not for the body. No need to be watching the phone there!)
(@Tyler_Hardy, dual-recording may possibly be a solution for workouts in the near future. Retrospectively, if you completed the workouts, you could insert a copy of each workout that disconnected, change it to the outside variant, & mark it as complete as though you’d done it via RPE. AT should still work, PLs should remain intact, but those past workouts just won’t have the data for AI-FTP detection to work. If TR disconnected early into the workout it shouldn’t upset your TSS by much. If you didn’t complete the workouts, I think you’ll just have to leave them as they are. Fill out the survey as cut short because of equipment issue. It shouldn’t cause your PLs to drop as they could for a failed workout, but they may decay because of not completing workouts for a few weeks, if that’s how long you’ve been experiencing this.)
Then it happened to me again today whilst doing Boarstone, in the “Endurance 2” warmup period. I noticed it pretty quickly, so was able to reconnect all devices, resulting in an extra 17 seconds recorded on my head unit. Firstly, data from TR sent to Strava to compare like-for-like, 3’00" duration:
And the data from Lezyne head unit on Strava over the same time period, 3’17" duration. As you can see it’s not a sensor issue as such because their broadcasts all continued to be recorded by Lezyne:
