Where do you see this? My fit file from ZRL Tuesday still have not been pulled. Some others in same race has i can see. Strange…
Just looking around at the results to see where the blue lightning bolts end and the queue notifications begin. There seems to be a separate(?) issue with TTTs not updating from the live data to the .fit file (even though it is public) for some riders.
I hear they spent it all on a couple of NVIDIA 3090’s and a PS5. Damn scalpers.
65,158 fit files pending.
2 Likes
That is more of an issue with those specific events. Zwift don’t make it easy for Zwiftpower to fetch the fit files. I believe these events hold teams in the pen to well past the start of the event which causes zwiftpower issues with the fit files.
If this is the case, how come some of the riders have got their fit files pulled? Even in the same team, and all have public profiles. This is not just the WTRL events.
Can you explain a bit more what is causing these problems? Is the coming maintenance fixing this? Would be good to have some more info and not just silence.
Hey everyone, a quick update for you all on this one: we’re aware of the issue with .fit files taking ages and of the substantial queue for them to be processed that some of you may have noticed. The long and short of it is that it comes down to a site design - meaning the code - that basically only allows for a certain amount of files at a time to be processed. We are doing work on this on the backend to make it run more efficiently and effectively, which should mean that in the coming weeks we don’t have this issue any longer.
As many of you are likely doing, our engineers and others here are taking much deserved time to be with their families and clear their heads during the holidays. You’ve all been along with us for this journey, and the whirlwind of ZwiftPower events you’ve been witness to is mirrored on our side; there’s a lot to manage and we understand how critical the site is as a tool to you, and we want to make sure we get it right; when we have it worked out, we’ll roll it out. For now, your patience and understanding are appreciated.
Enjoy your holidays, and may you all find strong legs!
Ride On.
14 Likes
Maybe if you’d not dumped on the guys who created and maintained it, you’d not be still figuring out how it works at Christmas time, coming up on six months after taking over.
Just a thought.
16 Likes
Thanks for the update. While I certainly don’t expect anyone to cancel their holidays to refactor Zwiftpower, I’m afraid that the mere fact that it took over a week to even acknowledge the issue speaks volumes about where racing is on Zwift’s list of priorities. Still, good to hear that things are at least in the works.
14 Likes
Does this also explain the lack of a GC for the Tour of New York?..
2 Likes
No, ranks for either Tour of New York or the comming Tour of Zwift on ZP
1 Like
Thanks Martin, but where? I see the individual standings per stage but it freezes at ‘loading’ when I go to leagues > tour of New York…
I can’t see why they couldn’t easily change the code to store the .FIT files on a network share (e.g. EFS at AWS) and then have a scalable group of servers to handle the processing from there. With the scalable group increasing/decreasing the number of servers needed as and when required. It’s not as if that’s a particularly difficult thing to do, especially with their resources - unless the .FIT file processing was implemented by a developer no longer with them since the acquisition, and it’s using some special magic and nobody has been able to understand it yet. That would be my guess.
Still waiting on getting sundays stats, so that’s 3 days and counting … getting a bit silly, as the outcomes of the stats breakdowns could impact a category upgrade/downgrade for some riders.
2 Likes
The developers didn’t follow with the ZP acquisition, and whether the code is spaghetti or not, it certainly isn’t going to fix itself. Guess the first update was just about the front end.
Now processing files from Friday.
2 Likes
Still waiting for the 6am Pacific time Tour of New York Stage ONE on Friday! Four days. And every time I go to the results page I get “Next update in 3 days”! WTF? Apparently not bringing the ZP developers along with the code is biting the rest of us in the ass.
From all indications, including Flint’s “Explanation”, Zwift really doesn’t give two shits about this. If it was important, they would have a team on it, holidays or not. That’s the way REAL companies run…
Not happy… 
4 Likes
Maybe if they hadn’t screwed those guys over they’d still be happy to help.
2 Likes
Just to add to this … and to keep this thread at the top of the list…
I notice ZwiftPower site, in general, is running very slowly and I am also still waiting for events to process dating back to Sat 19th. (Never had such a long wait for events to process!)
Crazy to think how big the backlog could get over the festive holidays… oh well… I love the Zwift platform and just want to see everything ‘work’ but this seems to be another example of where Zwift should really be more aware of the key community tools and be agile enough to respond/rectify quicker…
Merry Christmas everyone
3 Likes
That’s a bit like me paying for a hotel reservation and when I complain about the dirty room, the manager says “like you, the cleaner is on holiday, we’'ll clean it in a couple of weeks when they’re back. We have however still got enough staff to bank your money.”
14 Likes
All Right! The Tour of NY event from last Saturday was updated! Only took them FOUR DAYS and NINE HOURS! I’m guessing the Stage 3 data from Sunday will be our Christmas Present from the staff at Zwift…
I don’t think anyone is expecting your engineers to fix your systems during the holidays. But maybe some time during the past 6 months or so would’ve been a good time.
11 Likes