Cannot make waiver claims 09/27/26

I went to see if I’d won a waiver claim and at first thought I didn’t since it would have made me illegal. But no teams are showing red in our standings page and the system is letting me view lineup pages which it usually does not when you need to cut someone.

League:

Team(s)

My team: https://ottoneu.fangraphs.com/186/team/1490

Another I noticed is over on roster spots but not showing red: https://ottoneu.fangraphs.com/186/team/1492

To piggy back on this issue. I think there’s a bug with waiver claims. I’m unable to submit a claim for a player who was dropped during the day Saturday. The waivers have a 24 hour window so it will clear before sunday night 11:59pm.

However, since we’re within 24 hours of the season being over, it thinks i need a full 24 hours to claim a player.

Below is my league Julio Rodriguez was dropped on 9/26/26 at 5:49am. His waiver period is set to expire at 9/27/26 at 5:50am. This is in a few hours and well before the season ends. However it no longer allows me to submit a waiver claim for him.

Fairly certain it’s somehow already swapped into offseason mode. I’m in multiple leagues, and all waivers and auctions suddenly went away (as I was actively checking my bids). Daily stats are also showing incorrect team totals - which I think are based on last year’s totals. So it’s a big problem, but hopefully a quick fix.

looking at the daily stats page, not just the totals are off, but the daily stats are from games last year.

My theory: the Chicago-Boston game originally scheduled for 9/27 was played on 9/25 and the game they will actually play on 9/27 is the 9/26 game. Originally MLB games for 9/27 play at the same time. So with a game from 9/27 registered as complete, the system may think the year is over.

Should be able to make waiver claims again. Auctions are well over, and anyone cut after 11:59pm yesterday won’t be claimable.

Please start a new topic instead of “piggybacking” on unrelated stuff.

2 Likes

thanks!

1 Like

Misread the posts- all issues related here. Sorry about that but I think we are good now

thanks seems like it was fixed