Has anyone had issues with the sheets getting stuck on loading when entering the team IDs? Been having this problem the last few days and I am not well-versed enough with Excel/Sheets to know what to look for.

Posted by ja_tbfl on 3/3/2022 9:05:00 AM (view original):
Has anyone had issues with the sheets getting stuck on loading when entering the team IDs? Been having this problem the last few days and I am not well-versed enough with Excel/Sheets to know what to look for.

Same issue... I've even tried re-copying the from the original thinking I might have messed something up...

I'm guessing the issue is on the HD side of things. The Google Sheet is trying to pull the info from the WIS servers and there is some sort of slowdown. I'm not sure if there is anything to do except try again in a few hours.

I looked at my spreadsheet (which cubcub's is based on) and it sems to work OK for me here. If the teams don't exist (like during a season rollover ..or maybe stuck in a partial rollover event) that could cause an issue. Basically, it should work if you can look at the team in the browser.

It specifically uses the non-logged in link .. like this;
Hoops Dynasty – College Basketball Sim Games - Team Profile (whatifsports.com)

I just checked on all 4 of my teams. Phelan loaded right away, but Allen, Rupp, and Crum were stuck on loading. This is using Edge browser (if that makes any difference). None of those worlds are experiencing a rollover right now.

I wonder if it has anything to do with the dev team's recent work on the code base.

My team that works is in Wooden .. let me try one of the worlds you are having issues with. I had no issues opening up a team in Allen (I was also using edge).

Maybe the issue is transitory.

I'm in Naismith, Crum, and Iba. Iba worked this morning, Crum did not. Neither Iba nor Crum worked yesterday.

Wooden, Allen, Tark, Iba are working for me.

Rupp and Iba are working for me. Phelan, Allen, Crum, Smith, and Wooden are not. Using Sheets app on Android.

Smith quit working for me and I recreated from from my Allen league. Now this morning, Allen isn't loading.

Also having problems now // I have tried with google chrome, edge, and firefox. Get the same errors once it starts in all 3. No idea what is causing it.

I do have my sheet also in excel (or open office maybe), but I have not used those in a very long time and they likely need much work to get going.

NOTE: I could not find any old excel sheets of my (not cubcub's) original sheet .. BUT .. I did find some OpenOffice ODS files . These also fail loading data. Whatever this is, it seems to be intermittent and it seems to be on the WIS end.

Maybe it is a new http to https forwarder (all the sheets use http .. at least mine do. I tried switching to https and that did not help.

Another observation .. now all my sheets are working again, so it is very intermittent.

I know it has nothing to do with my internet connection. It does not seem to be a load issue, and when it is broken, my web browser can still open the roster in question, so it is not unavailable for all requests.

Seems to be no rhyme or reason to it. Iba and Naismith worked yesterday for me, Crum did not. Today, none of the three work.

like 5 months ago that dynasty list program i had started taking errors. it used to load every page successfully, virtually every time. 30 worlds of about 300 teams, there's about 10K page loads in there. it was reliable enough that i had a check to basically bomb out if any single division failed to load, ever. i had to basically completely take that out, because it almost never succeeds reliably now. it seems mostly d3 for some reason, but 1 to 5 d3 worlds will seemingly bomb out (i have not looked closely so this is probably small sample size). now i have that program just move forward every time, figuring the broke ones (which are still there, just outdated) will fix themselves on the next run, or the run after that.

i am only paying 5 bucks a month for the server this runs on, so i kinda figured it could be anything causing the problems. i forget if i actually take errors on the WIS page loads or not, i'm actually thinking its a no, but i haven't really looked in months (and i barely looked then). i think what i saw was... there was no hard page read error, which would have happened on a hard HTTP connection error or that sort of thing. i definitely remember being confused, i didn't have any errors of any kind... after a few minutes of reflection, i am basically sure this was the case. i have had page loads fail in the past, like 10 years ago it used to fail like 1 out of every 200, just because WIS servers sucked. but those were always on connect, so i have connection retries, but i don't validate the page load didn't get interrupted, that sort of thing - it looked to me like i was just getting incomplete data, and then some reports were failing to create, silently because i was very lazy about error checking and stuff.

anyway, sounds to me like the WIS servers are bailing on page loads early for some reason. this even happened to me a few weeks ago in game, and i got a wildly different color scheme and stuff on my team (this used to happen back in the day, but i hadn't seen it in so long i totally forgot). it was actually way better, i was really excited it was intentional for a second! but alas. anyway, it does seem to me that there's some issue on the WIS side, maybe some race condition, the application needs to flush before closing a connection but isn't, something up that alley. i could procure the dates on when this started happening on my end, i believe... sounds like someone really needs to open an inquiry with WIS on this one.

this tuesday's run looks exceptionally terrible. there's supposed to be 435 good files. i was seeing like, 431, or maybe 410, that sort of thing. last week there were 427. this week there are 153.

its impossible to translate that to a % of bad page loads - most were likely good - if any of the 300 or whatever teams in a division are not loaded properly, the whole division's reports crap out. so mostly this is still a low % problem, which only becomes highly visible when a substantial number of calls are being made? or perhaps large ones? not sure...