I merged your post into a discussion already under way. We are in fact working on a fix for this on the server end that we think will improve this bug.
The fix is not complete yet - we’ll update this thread when it is, and ask you all to keep an eye out to see that this no longer happens.
Just updating you that we also still have this issue. Could it possibly be due to the timing of entering the pen before the event start time? IE: If you enter under 30 seconds before start.
It’s definitely tied to it; this is why I don’t usually join the events I’m a beacon on until 1 minute to go.
It doesn’t seem to be device dependent though; as other Windows users have the issue and I don’t think I have.
But essentially it’s just like some people who are in the pen for long enough, a red beacon might not “step up” to the next person higher on the list, but get stuck from the first red arrival.
As red beacon if I left logging in until the last minute or 30 seconds then we usually had 2 or 3 other red beacons. Last time I logged in 12 minutes early before just about everyone else and it was the first time ever that I was the only red beacon (the ride has only been going for 3 or 4 months). Every ride for the last few months we have had multiple red beacons when I logged in usually less than 1 and a half minutes to go. I use windows for Zwift.
yep it does seem rather random. we even tried getting the wrong beacon to leave and late join again and they still stole the beacon back in some (but not all) riders view