I am at least in email contact with them - they have asked for my logs.
1 Like
Support have said this today - “I’m escalating your case to our Tier 3 team. As our leading Zwift experts, they’ll be best able to help”.
So maybe we’ll get to the bottom of it…
Thanks, Paul! I haven’t gotten any further correspondence aside from the one “we’ll look into it” email, so I’m glad you seem to be making some headway on this.
After all the emails I have ended up with this
Our team is aware of this issue, and we have logged it into our database. While I do not have a timeline for this fix, we will implement this on our end in a future update.
which is what we all knew in the first place…
1 Like
Oh boy… I want to say more, but I won’t.
Thanks for sharing Zwift’s response (and apathy) with us, Paul.
1 Like
I’m confused as to why this is still not fixed? Well, I’m not really confused, as it’s pretty obvious where Zwift’s time and resources are focused, but resolving this issue would sure go a long way to making the Zwift experience more enjoyable again for some of us who used this feature in the past.
The same can be said about many issues within Zwift, but they have other priorities…
3 Likes
Oh, Ben, I absolutely 1000% agree with you… I’m finding it really hard to keep my mouth shut lately.
1 Like