Its been mentioned in post 3 and 4 in this topic, but happy to share it again.
It is only the colorslider that remember the color. There are a few frames that have different paintjobs. Like the Pinarello Dogma F where I have 3 paintjobs for. The standard blue, the orange from the 10 year anniversary and the red one we got recently.
If I change those paintjobs it works, but when I change to another frame and than go back to this one it gets reset to the standard color.
Apple TV users please note an update is available.
I’d just like to thank everyone at Zwift for creating all of this and making it fun! I imagine some of this if not all of this is tedious. Zwift is amazing. I remember days on my trainer staring at a wall. So thank you!!!
I of course would like to see some things updated like putting the ROTW and COTW in the companion app so I can put it in my plan and request to a friend to ride it together. Thank you Zwift! RIDE ON! 
iPad and iPhone users please update at your earliest convenience.
There was mention of that in my Tour Fever event yesterday as well.
Yes, it happened to me yesterday. I was kind of hoping my avatar would ride in reverse the entire race. That would be pretty comical.
I can confirm that this is still happening as well. I had riders facing in reverse today in the event paddock for the Tour Fever event.
@calfzilla @Dan_Kothlow @SteveR @Drew_Robinson
Can you please confirm if you were all riding La Boucle? Or did you also see this on Double Espresso?
I was on Double Espresso
I rode Double Espresso.
I did not see anyone facing the wrong way but it was mentioned in the chat
Thank you for confirming, and I am seeing at least 6 riders for @calfzilla’s specific event that were on 1.116.2 or 1.117.0 in the pen so that could be the root cause, but I’m still investigating with the team.
Yes that one. I late joined the double espresso ride today so never saw the pen
La Boucle running 1.118.2
Edit: fixed version
FYI I removed this release note:
There was a miss that caused this to prematurely make it to the release notes before an actual fix was implemented. Our team is still looking at improving this, but nothing actually changed in 1.118.0.
