The Mech Isle Mayhem route was great, but unfortunately the race was ruined by a finish line bug. This was the Advanced A category in the first available time slot. There are a lot of high racing score Zwifters who take part each week, so for those of us competing for the monthly GC, this is a pretty significant issue.
Since this is a flat course, we came into the finish together as a large group. Everyone launched their sprints, and a block of riders crossed the line within just a few seconds of each other. I moved from 16th to 6th and had a great view of the pack… but the final results had me in 13th! (Look at the red dots on the top right with only one guy off of the front)
Even worse, the first six riders that appeared from nowhere in the results were given a two-minute plus advantage over the rest of the field. That throws a huge wrench in the monthly GC before it has even begun.
You can see here with 2.6 miles to go that everyone is bunched and no one is off of the front. The person that took first with a two minute lead can be seen at the bottom right row of Zwifters. Nothing untoward on his part, just a glitch. No one distanced the group from this moment on.
I checked the Strava segment afterward, and those six riders did not finish two minutes ahead of the lead group. In fact, the rider who was awarded 1st place with a two-minute advantage is 60th on the Strava segment for today. The true winners of this race were robbed by a glitch.
It’s a really disappointing start to the racing series, especially for those of us who enjoy competing for the monthly GC. Hopefully the results can be corrected, because a two-minute error like this will have a major impact on the standings for the rest of the month.
Another Zwifter from the race looked into this and noticed the top six with the 2+minute gap completed 1.2 miles less than everyone else. In the Road to A livestream, they can be seen at ~0.0 w/kg. Look at A.LLEN, T.Nilsson, and McCormick here below. They are behind Road to A, yet somehow finished top of the table.
I’m seeing a big 2-3 minute gap on the third Advanced A race that just finished. Luke from Rough Draft on YouTube was there so we should see the race posted later today.
I saw a video from someone that was on the glitch side of this, and he was racing to a different finish line with no other Zwifters around him. He ended up in first place.
This also happened in the 20:10 race. A group of riders was classified as finished around 1.5 km before the actual finish line, completely ruining the final results.
After watching a few race recaps and talking to other Zwifters, it looks like the bug is that Zwift is presenting an alternate finish line to a small handful of racers about 1.2 miles before the actual finish. Those riders launch their sprints, completely unaware that everyone else is pacing for a finish that will happen more than two minutes later.
Zwift is still logging those early finish times and then placing everyone into the same final results table. This explains the massive gaps and incorrect finishing positions.
Zwift needs to figure out why certain riders are being shown a finish line that is not the actual finish for the new Mech Isle Mayhem route. Until that is fixed, race results on this route are going to be completely unreliable.
I did the 19:10 UK time stage one and as I sprinted for the line I saw i was in 6th as i crossed the line, Buzzing or so I thought. When the result came through riders 3 minutes in front appeared on the results page on zwift racing and zwift power i was then placed 17th. Knackered my velo score now.so annoying. Did anyone else in the B category get this?
I’ve just finished the race.. fought like hell, finished 4th… And after the race zwift companion showed that I’m 16th.. Very disappointing.
Is it possible to somehow correct past race results?
