Bug in TTT today

[Bright]

Hi guys,

Can thedata of the TTT be checked? I was in the lead and 3kms before the end I set mologne to wait for him no and somehow my guys wanted for Pantalon, which is crazy because he wasn't even in my screen.

Id really like the data yo be checked, because I didn't touch his settings, why would I?

Kind of screwed up everything....

[flockmastoR]

Hi guys,

Can thedata of the TTT be checked? I was in the lead and 3kms before the end I set mologne to wait for him no and somehow my guys wanted for Pantalon, which is crazy because he wasn't even in my screen.

Id really like the data yo be checked, because I didn't touch his settings, why would I?

Kind of screwed up everything....

Hey Bright!

First of all, I understand your anger. I have a few questions to you in order to understand the data better.
1) Did you have more than 1 active tab open (Smartphone in parallel)?
2) Did you do any setting changes in the "tactics" tab (the one that shows the normal race tactic fields), like put in fighting there (ps I am not entirely sure if that is even possible/active during the TTT)
3) What other settings did you set at that point? Which riders did you not/wait for from that time on?

[Alkworld]

2) Did you do any setting changes in the "tactics" tab (the one that shows the normal race tactic fields), like put in fighting there (ps I am not entirely sure if that is even possible/active during the TTT)

You'd see that in the log. But we saw only the TTT settings, back and forth in short sequence. It might have been that one response overtook the other and only showed the later setting. Maybe two different settings were done too quickly after each other, without waiting for the actual result.

[Robyklebt]

Talking out of my ass, but:

I was in the lead and 3kms before the end I set mologne to wait for him no

Could it be that too many were on waiting "no"? Meaning 5 riders? And then it becomes "waiting for everybody"? Or can't you even set too many on waiting "no"?

[Bright]

Hi guys,

There werent any additional settings except for the intensity of the other riders, I did change their intensities every km depending on uphill/dh/pave and flat. Everyth8ng went fine until 3 kms before the end when I switched Mologne to wait no. I was on my mobile, didnt have any other sessions open.

Pimieu Pantalon was set on wait no from the start and I set mologne on no on the km it happened. Hadnt checked Pimieu Pantalon during the race as he was not playing an actual role in this ttt amd I presumed he would be fine timewise.

Dont know if I can tell you more as it seemed straightforward. I'm extremely bummed it happened as I was winning the ttt with 15-20 seconds or so and this will hurt my income severely this tour.

If it can't be fixed (which I presume isn't possible, and maybe not fair for the others, maybe another solution is possible like withdrawing my team from the tour and compensating me for the first day loss, though I don't know if that's possible either.

I understand it's no-ones fault, just feels really crappy especially since it's not like 20 seconds lost but 7 minutes, keeping me out of contention completely.

[Alkworld]

What's technically possible and what's not?

• GC time correction only for Bright would be easy
• financial compensation only for Bright would be easy
• correcting whole stage result (Bright winning, palmares entry, financial corrections for everyone, jerseys assigned to other riders) would be too much work

Now the question is what is the right thing to do?

From the technical / software perspective, there wasn't anything going wrong it seems. In the new version, which I'm working on still, there'll be another check when you're not waiting for enough riders (< 5), but I don't think that would have helped here. You'll still be able to wait for a rider that's already far back.

[flockmastoR]

Hi guys,

There werent any additional settings except for the intensity of the other riders, I did change their intensities every km depending on uphill/dh/pave and flat. Everyth8ng went fine until 3 kms before the end when I switched Mologne to wait no. I was on my mobile, didnt have any other sessions open.

Pimieu Pantalon was set on wait no from the start and I set mologne on no on the km it happened. Hadnt checked Pimieu Pantalon during the race as he was not playing an actual role in this ttt amd I presumed he would be fine timewise.

Dont know if I can tell you more as it seemed straightforward. I'm extremely bummed it happened as I was winning the ttt with 15-20 seconds or so and this will hurt my income severely this tour.

If it can't be fixed (which I presume isn't possible, and maybe not fair for the others, maybe another solution is possible like withdrawing my team from the tour and compensating me for the first day loss, though I don't know if that's possible either.

I understand it's no-ones fault, just feels really crappy especially since it's not like 20 seconds lost but 7 minutes, keeping me out of contention completely.

From what I saw in the data pantalon was set to not being waited in the beginning but set to being waited during the race. Will provide all of the actions later on. But my impression was, that you tried setting him on wait true on that 3km to the end km but this setting was immediately overwritten again with his previous settings to be waited for. Can provide detailed data later

[Bright]

I don't know what happened exactly, but I hadnt checked on pimieu Pantalon until I couldn't find my team anymore (it was when I wasn't in first place and scrolled down. )

What happened in the last km I really don't remember, as ai was typing in chat asking what happened,but by then it didnt matrer anymore anyway.

I know I don't have any proof, but would be no reason for me to check on Pantalon as he was behind and my team was winning.

Tour is over for me anyway,so doesnt really matter now. It's just immensely frustrating.

[flockmastoR]

I don't know what happened exactly, but I hadnt checked on pimieu Pantalon until I couldn't find my team anymore (it was when I wasn't in first place and scrolled down. )

What happened in the last km I really don't remember, as ai was typing in chat asking what happened,but by then it didnt matrer anymore anyway.

I know I don't have any proof, but would be no reason for me to check on Pantalon as he was behind and my team was winning.

Tour is over for me anyway,so doesnt really matter now. It's just immensely frustrating.

Yeah, doesn't make sense, but wouldn't rule out that a misclick happened. After the last km Pantalon for sure had the setting to be waited (could be seen in the tactics menu). You said, that you checked the settings to be valid when going off, so I was just trying to find out if there are possibilities that you see (inactive) old settings or you just overlooked it (you said you went off, maybe time pressure when doing settings/checking settings is the most likely explanation).