I think I might have figured out what caused the Bluetooth Connection Failure with my Radar Pace last night during the ride... there's two scenarios that I was able to put together based on the Time into the ride & the Distance into the ride; both of which lined up with 2 different points on the ride data from my Garmin:
1) The Pace locked up pausing/un-pausing the workout at the Stop sign, at 44:44. (Yes, we stop at them.)
2) The Pace had a communication failure just as we passed under I-295, at 15.6mi; there is a known cellular dead-spot as you are coming off the bridge that drops phone calls every time. It's really bad.
I am thinking it was 2), as this was some serious interference that wouldn't allow the Pace to reconnect.
And interestingly enough, looking at the Workout Detail from the Radar Pace App... look at the Distance & Elapsed Time, very close to passing by the cellular dead spot.
The Bluetooth connection is how it talks to the phone, but the App uses the GPS for location services for the mapping. During the ride, the music would skip in and out every now and then, but always picked right back up. I have had other Bluetooth sport headphones that do this as it's a distance thing, and my phone is in my back pocket. So I didn't think much about it cutting in and out during the ride. (It's wasn't that frequent it did it, but it was at least 5-6 times) When we were passing this spot, 15.6mi, we were moving at 28mph... if it did skip a beat with the music playing, it would have been the last thing my mind was paying attention to in a pack of +30 riders moving at that speed. With the mapping feature having stopped at that distance, I am really thinking the cellular interference did a number on it. It's really a bad spot, everyone in our city knows your phone call will be dropped as soon as you get off the bridge; and this road we were on is less than 100yds from that spot.