Support email is preferred (as that guarantees theyâll see it), but theyâve also mentioned they are checking this thread for potential bugs as well. So really either works.
Perfect thank you.
Same issue with me. I did the outside version of my workout today using my wahoo head unit and it didnât give me a survey or change my progression.
To help debug issues, provide the exact workout where you had the problem, and what steps you did when the issue popped up.
@Nate Please Please Please can we have a specific Forum thread where ONLY formal TR announcements and updates are made. ONLY TR staff can post there. No one else can comment on them. Then have a separate threads where comments are made (that can refer to the formal ones). Trying to work through over 2000 posts looking for the important ones and the current status is a right pain. (I am sure it is a part of the current frustration with dates etc.)
Perhaps limit the formal posts to: This is a major update. This is the expected next beta group, This is a release. We have these bugs we are fixing in the Beta. These are our next planned releases. This is happening next⌠Then have a separate post for everyone to discuss it. That can always refer back to the formal updates.
I must admit I am getting fed up trying to sort out the wheat from the chaff (2066 posts) of this announcement. I have resorted to just looking for TR employee answers to things. Or simply not bothering.
Just an ideaâŚ
PS I have given up waiting for this AT release, I have read the runes of continued (and appropriate) bug fixes and decided to just not get excited until I can actually see in and try it for myself) and the proper final announcement that it is fully released. It will be ready, when it is ready. SimplesâŚ
Agreed - the cynic in me thinks they announced this in March (when it was FAR from ready for the masses) as its the time of year when most of the monthly subscribers begin to cancel subscriptions, and so they dangle the lure of AT in order to keep people subscribing in the hope of getting AT instead of cancelling. I bet there are vast numbers of people that will stay a subscriber believing they will get AT any day when in fact its still a long way off for them. Master marketing stroke by TR as holding on to subscribers has to be #1 strategy for all subscription based businesses.
If AT eventually really delivers actual âvalueâ for the weekend warrior it may finally be the way to keep many people subscribing for 12 months rather than just the indoor winter season. The holy grail for a subscription business with a very seasonal product. Outdoor workouts was part 1 but this is the jewel in the crown if they make it work as promised.
As you say, deeply cynical.
Personably I donât think it was planned like that but the net effect for TR is to retain subscriptions at a time they would normally ease off.
Nate was very specific in saying you could sign up for the beta without being a subscriber and that you could subscribe as soon as you were entered into the beta.
As for announcements @PhilSJones, the podcast each Thursday is your answer. Nate provides an update on people entered into the beta and an estimation of the next ones to add. They really have not been doing many updates on here or at all other than what is said on the podcast, so youâre not even missing anything major in this thread.
I agree about the announcement part. It would be much easier to follow. It would great for release notes as well. Now the apps are on a consistent code base I would hope to see more regular updates and following those in there own post would be very helpful @Nate_Pearson
Agree with post above that a huge problem in all of this rollout is no dynamically updated visibility to current status and known issues anywhere.
This particular problem they have with wahoo outdoor workouts also renders the fully released TrainNow feature useless if you use TR workouts on wahoo indoors or out.
Iâve been raising it for weeks and support acknowledged its a real problem. Meanwhile people keep saying TR outdoor workouts work, based on old info from Nate and others above, and itâs just not true for a very significant number of users who are discovering this piecemeal as evidenced above.
Now as to how we will know when itâs fixed? Who knows? There is no visible log of these issues being managed by TR.
Historically Iâve always thought TR had a huge edge in that while premium priced for what is a relatively simple app, it just worked all the time and was super reliable, had unique outdoor integration, and outstanding support and I have shared that view with so many frustrated zwifters. But the recent rollouts were rushed, half baked, too much at once and are not being managed well at all. Itâs a huge disappointment. Support is very responsive but has no visibility to fixes and itâs grossly inefficient for all of us to keep reporting the same known things with no way to see if and when they may resolve.
In my industry, customers would crucify this kind of rollout and execution. I cannot imagine going into a customer meeting on a new product rollout with no checkpoints, eta or status for anything. TR fans keep defending this as totally normal and acceptable and maybe that echo chamber on here is a bit too loud. TrainNow is not beta. Itâs out for weeks and not working for a huge segment of users for weeks because of issues like this.
Meanwhile, AT still being marketed on the forum banner. SMHâŚ
I mean⌠Itâs a beta. It is fully expected there are going to be bugs and some big ones at that. Only around 300 people are in the beta so itâs not impacting a large portion of subscribers, I would imagine.
Your experience in AT beta is not going to be optimal (thatâs expected) but it will make it more optimal when it finally releases to the masses. Youâre a guinea pig much like I and the other beta users are.
The champagne was probably too much and gave the wrong impression for how final things were, but overall I think they were correct to announce a beta (they needed users to test things). There should have just been clearer communication on how closed it would be and what it would entail.
I also think there should have been a private thread or forum for bug posts like there are with video game betas. That would allow beta users to follow any similar bugs and report additional info to streamline some things without the clutter of the rest of the users posting.
In case anyone wants to see how xert is reacting to adaptive training: (see comments)
My understanding is that TrainNow is full release and itâs plagued by the same issue - TR structured workouts done on the #2 market share head unit are just ignored. So you perpetually get the same off the couch suggestions. For what itâs worth, I donât have any access to AT but understand itâs impacting that as well - but for the vast majority that only get to use TrainNow, itâs disappointing that we have to do a bunch of tests and experimentation to figure out nope, it doesnât work.
Itâs also hard to fathom for example that nobody tried a TR outdoor workout with a Wahoo head unit before the big AT reveal and TrainNow release - and weâve got many statements since including from TR staff that this works - but it doesnât.
Still not clear if a FTP update totally wipes out all your levels or not - sounded like a bug that was going to be addressed - I lost track with so many mixed messages. Is a ramp test needed or not? Today or in the future? FTP changes are a pretty common use case to be very clear about. There is no central resource to say âhereâs the real live status right now on the many known issues that keep popping up - donât worry if you see them - weâre on it and are targeting this timeframe to have a fix out - check back in at this time for an update.â Podcast updates are not even close to this level of detail.
Agree that a more closed off and quieter/longer beta was and is still probably warranted to manage AT development.
But for the things that are released and should be working and have gaps affecting a lot of people, better status summaries would go a long way to restore some confidence. Even if dates slip, the engagement and communication would be appreciated.
Donât get me wrong - this will all likely be fantastic when done and Iâm excited to see it eventually⌠but this thread is a mess and there has to be a better way to communicate.
I misunderstood you were speaking directly about TrainNow and not AT. That is indeed an issue as that is a fully released feature at the point. I worry the issue with the outdoor workouts on Wahoo is relates to Wahoo firmware updates not not TRâs side of things. If that is the case, it could have very well been working inhouse and then a firmware update from Wahoo killed it after they added people. Not much TR can do about that if that is indeed the case.
It was serving ramp tests to people on the middle of the plan when it should not have. Not sure if it has been fixed but the answer from @bnied was follow your current plan if youâre on one and do the ramp test when it comes up on your calendar. If you are in the middle of the plan and are served one when you get added to AT, just do whatever was on your calendar for that day instead. If youâre starting a new plan, then it will give you a ramp test to start just like any plan without AT. Essentially user behavior does not need to change to make the most of AT.
Iâm also all for having some patch notes for each new AT release not unlike what we got for the Android and iOS betas.
I agree with the private thread for us beta users. There would be less clutter, more opportunity for users to compare notes/discuss, allow the TR team to focus on one thread. and most importantly allow the TR team to control the message a little better for the general user base.
Plan Builder would disagree. If you tell it you have 10+ hours to train and that youâve been doing structured intervals for âmultiple yearsâ you will be given High Volume SSB. This sort of cyclist is not that unusual.
Edit: mentioning this here as it makes it hard to use AT with Plan Builder, for me at least.
Hi all, so I made a youtube video of my current experience with adaptive training with my high volume SSB plan (I just finished week 1) so it should hopefully be a weekly series because the plan literally does adapt from workout to workout. Iâm not really prepared to share publicly just yet, so if youâre interested message me privately and Iâll give you the link
I am pretty excited to start the AT Beta this week! I am starting a new plan (SSB 1 MV) since the events that I am targeting donât hit until August. Looking ahead, I need a bit of scheduling advice. I will be racing Zwift Racing League on Tuesdayâs starting on 4/6 through the next several weeks. Basically those races are around an hour and primarily threshold. I am wondering what workout I would swap it for - my threshold session or my hardest sweet spot session? Also, should I associate it or leave it unassociated? Once AT starts accounting for outdoor rides this is probably an easier call, but until thenâŚ
Any feedback is appreciated
Swap the race for a workout of a similar effort (this is a best practice regardless of AT or not) but donât associate it with a TR workout as per the below.
Thanks. My initial thought was to swap it for the threshold workout since it is closest to the race effort, but it looks like the plan only has 1 threshold workout per week. Since it isnât including outdoor rides, I think AT wouldnât have any basis for adapting my threshold capability without me completing that workout. On the other hand, there are multiple sweet spot workouts. To your point, I probably should focus first on what is the best plan decision rather than playing to how AT will react