ASL is continuously improving the DFS Optimizer. We monitor software exceptions, investigate unusual behavior, and track user-facing issues even when they affect only a small number of customers.
That work has made a substantial difference. Over the past year, the rate of user-interface-related exceptions we track has fallen by more than 90%.
Our highest priority is always an issue reported by a customer. After that, we continue working through the less common issues that we have identified ourselves. Many are rare edge cases involving a particular slate, contest type or combination of settings, but we want to resolve those too. That is part of how we continue to battle-harden the optimizer.
Current Issues We Are Tracking
A few of the areas currently receiving attention include:
- Single-game and Showdown contests. Certain combinations of player locks can incorrectly result in the optimizer reporting that no lineup can be built. We are also addressing some Showdown-specific exposure and salary-cap edge cases.
- Recommended lineups and Auto-Team Stack. In uncommon situations, recommended lineups can return no result. Auto-Team Stack can also occasionally produce a lineup containing fewer stacked players than requested. We now have testing tools that allow us to reproduce these cases reliably as we work toward resolving them.
- Empty or unclear results. There are situations where the optimizer should provide a better explanation when no lineup can be built or when a table contains no results. Improving that feedback is part of the current cleanup.
- Multi-lineup and CSV tools. We are tracking several less-common issues involving custom-projection templates, exclusions and CSV import/export behavior.
- Data availability. Occasionally an outside data source can return a missing projection, unexpected player status or delayed update. We continue improving how the optimizer recognizes and handles those situations.
- SuperFlex slates. Some SuperFlex slates currently may not appear even though SuperFlex is a supported format.
The Optimizer Seems Slow
Some apparent slowness is not actually an error. Features such as Auto-Team Stack can require the optimizer to run many lineup calculations at once and recheck those possibilities as you lock or exclude players.
See How To Make The DFS Optimizer Run Faster for the easiest way to make player-pool setup more responsive. That article recommends temporarily turning off Auto-Team Stack and Exclude Opposing Defense while making broad player selections, then turning them back on when you are ready to finalize the lineup.
NFL Slates That Cross Week Boundaries
The optimizer currently does not support NFL contests that cross our NFL week boundary, such as various Monday–Thursday slates. Those contests will therefore not appear among the available slates.
What Is Coming Next?
Our immediate priority is continuing to clean up and strengthen today's optimizer. After that, we will progressively move toward the next generation of the product rather than replacing everything in one giant release.
See ASL's Next Generation DFS Optimizer for our current improvement roadmap and the larger vision of where the product is heading.
Please Tell Us When Something Doesn't Look Right
Being aware of an issue is more than half the battle.
If you encounter something that does not look right, have a question about how the optimizer is behaving, or want to tell us which improvement is most important to you, contact us anytime at
If you are reporting a problem, a screenshot along with the sport, DFS provider, slate and what you were doing when the problem occurred can help us reproduce it much more quickly.
We care about the user experience, and customer-reported issues remain our highest priority.