Leaderboard brokey ( Edit : Fixed! )

[Lia]

EDIT: FM have since resolved the issue, it seems they managed to retain everyone's streak from what I can see.

App isn't logging my streak again. Caught it this time and been riding around some more in the rain to try and get it to register but it won't.
Achievements noticed I rode between 11pm and 1am but leaderboard won't log the now 13km for today.

Feeling bummed, thought I was being careful not to let the app get me this time but it's not playing fair now :(
https://www.youtube.com/watch?v=vtIeU7QjQO4

[Lia]

It got me again...


At least this time I watched it happen and know I wasn't imagining the ride where I lost my prior one.
All I can say is I got cold and soggy for nothing tonight.

[HanahsDax]

@Lia Damn it! I noticed I rode 9 miles today on the V1 and it’s only accounting for 5. At some point today the server stopped accounting for any new data received. This has happened to me three times now, luckily after I already rode the minimum mile to continue the day streak but what rubs salt into my wound was it was when I went out for the Night Owl badge time frame ride which has been the toughest out of all the time based badges for me, I’m more of any early riser than a late nighter. Keep documenting your progress with screenshots daily.

[blkwalnutgrwr]

@Lia -- Wow. Irritating. Arrr... Growl... Have you tried powering down your phone and bringing up again? That sometimes works for me. Sorry for the lame advice to someone technically proficient!

[HorsePlay]

All - Hubby and I noticed the same today.

I noticed sometime mid-afternoon that Achievements had stopped adding to my miles ... but, gladly for me, after I'd already covered a minimum of 2 miles in morning riding. My later miles weren't counting (although they were 'recorded' on the Recordings tab). I figured the app would catch up at some point ... but it hasn't even after log-out, restart app, login, etc.

My husband just came home and nearly the first thing he said, "The OW app didn't count my miles today!! My streak is broken, again." He explained that he'd ridden four 1-mile laps around his office complex thinking, "This time, the app will reward me." Nope. Try again. Nope. Try again.

Somewhere in my afternoon horse care cycle I kinda figured that the OW folks were staging a Reset to give us all a good group headache.

@Lia , I'm so sorry for your day streak. :(

[HorsePlay]

So I wonder ... will this trigger a good number of changes in @Lia's weekend leaderboard review? Hmmm ....

[Flopmo]

My streak disappeared tonight even though I rode 1.7 miles...I was #24. I am so bummed out.

[HorsePlay]

@Flopmo , So sorry! #24 was a super accomplishment!

To all: Is there any hope that OW's App Tech Team will be able to restore the data and sort this out?

[Lia]

I think FM may have fixed it since I've woken this morning to my streak being there again?

Not sure if it was one of the myriad of things I tried before midnight rolled by or FM jumped in the back and rolled back the tables.

This has happened once before but the streak never reset at midnight and just delayed it's update. This was different as it did wipe the streak so I'm not sure if I can draw parallels.

Has anyone else's come back? I noticed my position moved to 71 from 87 so it seems others have still to get theirs back.

• Edit 13:75 bst :

Looks like everyone is slowly coming back, I've shifted down to 78 so those that lost a streak above me appear to be returning which is good news :)

However today's mileage hasn't updated again. I feel as if the leaderboard isn't updating properly. since sometime before 11pm bst.
Even more odd I started today with 8365km on the OD but after 2.4km I jumped to 8369km. Noticed after 1km I jumped 2km so I feel like my OD is doubling my distance
Realised this might just be the Miles -> Kilometre conversion thing in play.

[Flopmo]

@Lia No such luck for me, still showing no streak. Glad to see some are getting it back though!

[LidPhones]

@Lia My steak stayed on the plus and jumped to 13th with 14 days sequential.....

[Lia]

@Flopmo Seems like the issue is still present, I'm unable to update mine since it updated last night. I'm seeing more rejoin above me so I suspect you might get updated too soon.
Wonder if the server responsible for ingesting the new data is crashing and only works once given a kick.

Some users on Reddit have noticed too. I imagine FM will put a fix in place since it appears to be affecting everyone.

@LidPhones That's quite an impressive leap, what was it like prior to the issue?

[Lia]

Might have found something.
https://app.onewheel.com/leaderboards.html

Within the source of the leaderboard there is a broken segment. I wonder if this is enough to completely crap it out.

I know veeeery little about code but checking this against my weekly logs of this page I can confirm this broken element wasn't throwing an error on Saturday.

[HorsePlay]

This morning's ride, for me, has not caught up on the Leaderboard/Achievements tabs. I recorded it, screen captured it, (etc) and will hope for some magical back-end (server) catchup cycle to wake up.

[Lia]

@HorsePlay Seems we're all in the same boat, which at least is re-assuring in a bizzare way.
Apparently some are having issues recordings rides too although I haven't tested that myself yet.

Best of luck to FM finding the issue.

[halfquart]

I'm having the same problem today. I've gone on 2 rides today. Both have successfully auto-recorded under "Rides" in the app, but not being picked up in the rankings when i go to the "leaderboard" or "achievements". I just did a lunchtime ride and it didn't get picked up by the lunchtime achievement counter. I'm less concerned about the achievement counter though....my streak was 173 days yesterday...
My streak ranking was at 38 yesterday. This morning it jumped up to 28.....then moved to 29....and is now at 30. I find it impossible to believe that 10 people in the top 50 streaks didn't ride yesterday.....just saying....
There's something broken....somewheres.....

[NotSure]

@Lia Sources available to web clients like browsers aren't usually the same as those that actually govern the backend. It would be very bad practice if they were! However, if the master does share the same code, and someone fussed with the stack on the backend, then maybe there were some cross compiling errors that could show themselves in a client resource later, but I'm just speculating. Debug is a drag.

My best guess is that the apps lightly authenticate with a web api, then relay data which is in turn cached for leaderboard ETL later. Those scripts are maintained actively so it's probably just a bad fork or something that inadvertently went to production. Hopefully they can retally after they find the bugs.

My cat walked across my keyboard once and erased half a day's work. Could have been dire if I were afk at the time. I may have never noticed it. Could take hours just to identify the error at that point, let alone address it.

[Lia]

@NotSure Thanks for the insight, that makes sense.

Went back over it and it looks like the same lines are present (I must have been looking at the wrong tab earlier) but for whatever reason it's just unhappy. As you suspect it's probably something in the back which the web client doesn't show.

Will have to just wait on FM I guess.

Sorry to hear your cat did that, it's insane stuff like that can happen.

[LidPhones]

@Lia went from 16th to 13th with the glitch. Also just did a 1.1 mile ride to stay at 13th but it seems the FM servers are still no 100%. I have the ride recorded but in rides but still shows expiration at midnight.......

[LidPhones]

@LidPhones Yo ME! FM servers linked up and I slide to 14th and got 2 miles credit for my 1.1 mile ride.
?????