Dropping Active Starters via Waivers
If a team manager in your league drops a player from their starting lineup after that player's game has already started, this is an intentional platform design, not a bug.
Example Scenario
Imagine you submit a Friday waiver claim for Emmett Johnson, choosing to drop Braelon Allen. The system indicates that Johnson will clear waivers on Sunday at 2:00 PM EST.
However, Allen’s game kicks off earlier at 1:00 PM EST that same Sunday, and he is already locked into your starting lineup.
When you win the waiver claim at 2:00 PM EST, the following happens:
Braelon Allen is dropped from your roster mid-game and receives an "Off Roster" label.
Because he was already starting, his lineup slot locks
you cannot bench him, but his points will still count for your team this week.
You can now insert Emmett Johnson into your starting lineup for the current week, but only if Johnson's game has not yet started and you have an open, eligible slot (like a Flex or RB position) available to use him.
This scenario can only occur if the waiver claim was submitted before the dropped player's game began, and processed before the new player's game starts.
Lineup & Points are Locked
The dropped player remains locked into the starting lineup slot for the remainder of the week. Their stats and fantasy points will still count toward that team's matchup total. The player will simply display an "Off Roster" label.
The Added Player
The newly acquired player can only be started that same week if their own game has not yet begun, and the manager has an open, eligible slot elsewhere in their lineup.
Strategic Trade-offs & Risks
While some managers may try to use this timing to their advantage, it comes with significant risks:
Roster Disadvantage: The manager has to drop a player who was talented enough to start in their lineup.
Asset Consumption: The manager must spend FAAB or sacrifice high waiver priority to make the claim.
