Your rides should all be there when this is fixed. Worst case, if for some reason the server didn’t like it, you have a local log file that we can use to recover the ride.
@Nate_Pearson We appreciate the quick response and ongoing updates. Your team is awesome. Also, it’s great to know the workouts aren’t lost.
not only that… i completed a major ( for me) 2hr workout and at the end when I finished it tossed it away as if I never did!! i f’ng furious .
then the login issues started,
Was able to log in on the mobile app but not desktop. Also on the mobile app tried to update calendar and move today’s ride to Saturday, but received the message “Request failed with status code 500”
Thanks for all your help TR crew
same…super pissed. it was a hard one that would’ve told me a lot about where I stand on my training.
100% my problem. Hopefully they can recover it 
I’m in Australia so mid arvo here now. I can log in but can’t open any workout (just says it’s loading and does nothing). I also tried to move a workout to tomorrow and got an error message. No problem as I can see what to do in the description and can head outside. Hope you get some rest Nate, must be late over there now!
All sorted - not a bad response time for whatever it was 
so all good for me here in Australia
Uh oh, This is how it begins. SKYNET IS OFFLINE!
I can’t believe this! I did ftp test and went from 270W to a 550W ftp! Now it’s not there and it’s showing 270 still. Come on Nate! Nobody will believe me now 
@Nate_Pearson i am unable to login…says wrong username or password and it won’t let me rest it
Azure database is full and won’t let you write… oh well it sounds to me as a developer it’s more of an issue in fundamental backend design lacking scalability, rather than from Microsoft Azure’s hiccup.
In such a case, similar things might happen in the future even when you resolve this time.
Sorry for being negative and I hope it’s not the case😬
from the comments above they have a workaround in place to let people log in and ride. Anything that writes new data - Password resets, creating plans and ride syncing will require writing new data up into their Azure database which is where they have the issue.
Good news is that it seems like a configuration issue with the Azure databases that host the application and all the data, rather than the TR product itself.
Patience and empathy is required here. Im sure a few people are having a stressful night. I’ve been in the same situation.
As a developer … not really, the transaction log is a integral part of the sql database and is used to record what has happened, it is not the data, so when you do a back up, it should be possible to clear the transaction log, it doesn’t really signify anything in the backend design lacking scalability of TR, rather a failure of the transaction log to be cleared
We don’t really have enough info from Nates post, was it because the transaction log was to small (in size) or had it failed to clearer records from 11 years ago, which would have been redundant if TR is doing weekly backups, and this could be a failure of a pipeline to run in Azure, or TR failing to set it up, again, not enough info in Nates post to judge (but from my experience of Azure today … I could guess)
More info on transaction logs
Thanks for the in-depth info. Still not enough explanation for the ongoing issues I’m experiencing with TR now, but I have no intention to argue here since Nate’s post has so limited info.
Anyway, TR team might have to come up with full explanation what caused this problem once they get it fixed, because this type of outage can rarely be seen in modern web applications with modern technologies and dev process.
Well I don’t need a full explanation. It was broke. They fixed it. Enough said. They can explain but I don’t feel I have the right to that information. I also don’t feel the need for that information. I also probably would not understand the information. Also what am I going to do with the information? Brow beat them with a tsk, tsk, tsk? How dare you mess up your azure database on a Friday night and it took you over 15 minutes to fix it. This is the first outage I can think of in my 5 years or so at trainer road.
I mean its not like its xmas time and our flights got cancelled for days and they lost our luggage and we slept in the airports for a week.
Frankly, any organisation shouldn’t be sharing technical information in public that would potentially leave them potentially open to a cyber attack and ransomware. Unless forced to by legislation.
Especially so when SaaS is the core business.
That said, If trainer road ever get hacked (god forbid) they might have to diversify into merchandise to make some money, so a lot of people will finally get their wish… 
your body still did the work 
I woke up this morning to my ride being synced up with Strava. Hooray! Thanks TR team! Awesome.
@downbeat007 Same for me. It was like Christmas 
…
. Seriously though, a big thank you for the quick response by the TR team.