Why we don't analyze some hands
Not every hand you upload to FlopHero gets a full GTO analysis. You might notice that the number of "Available" hands in your database is sometimes lower than the total "Hands" in a session file. This is intentional. We filter out certain hands that don't offer meaningful learning value or can't be solved with reliable accuracy.
Understanding which hands are excluded helps you focus on the spots that truly matter for improving your game. It also ensures that your performance metrics aren't distorted by automatic or unsolvable situations. Here's a breakdown of why some hands are left out.
Hands without strategic value
Some hands end before you have to make a real strategic decision. For example, if you fold from an early position before anyone else has entered the pot, or if everyone folds to you when you're in the big blind, there's no choice to evaluate. These automatic actions don't provide any insight into your GTO performance.
Including these hands would clutter your results and could skew your overall data. FlopHero prioritizes hands where you faced at least one genuine strategic decision, as these are the spots where you can actually learn and improve.

Limped pots and solver complexity
Multi-way limped pots are notoriously difficult for GTO solvers to handle accurately. The vast majority of modern PLO solver work focuses on single-raised or 3-bet pots, as this is where the most strategically rich and common scenarios occur.

When several players limp into a pot, the number of possible actions and outcomes grows exponentially, making it computationally impractical to solve in real-time with high accuracy. To maintain the reliability of our analysis, FlopHero excludes these complex, multi-way limped pots. If you find yourself in these spots often, your time is better spent studying the more common raised-pot scenarios where accurate GTO models exist.
Incomplete or corrupt hand histories
A hand can't be analyzed if the hand history file is missing key information. This could be anything from a street's action to the final board cards or stack sizes. FlopHero needs a complete and valid hand history to construct the decision tree for our solver.
Missing data can happen for several reasons:
Glitches within the poker client
An incomplete export process
Incorrect hand history saving settings
If you notice a large number of your hands are being skipped, you should first check your poker client's settings to ensure it's configured to save complete hand histories. For more information on uploading hands, see Hand Upload.
Scenarios outside of solver coverage
Our solver library is massive, covering millions of common preflop and postflop scenarios. However, some rare situations will inevitably fall outside of our current solver parameters. This can happen with:
Unusual effective stack depths (e.g., very short or very deep)
Rare or unconventional preflop lines
Uncommon board textures in niche situations
Our simulations are focused on the most frequent and impactful spots, such as stack depths between 40-200bb, standard open-raising and 3-betting sequences, and heads-up or 3-way postflop play. If a hand doesn't fit these or other supported criteria, FlopHero will mark it as Not Analyzed to protect the integrity of your data.
How to maximize your analyzed hands
While you can't control every factor, you can take steps to increase the percentage of your hands that get analyzed. Focusing on solid fundamentals will not only improve your GTO compatibility but also strengthen your overall strategy.
Open-raise instead of limping. This creates more easily solvable, raised-pot scenarios.
Play within standard stack depths. Try to maintain a stack between 40bb and 200bb where possible.
Focus on common lines. While creativity has its place, building your game around standard, fundamentally sound lines will give you more opportunities for GTO analysis.
In your Session Dashboard, the "Analysis" column shows how many hands were evaluated versus the total uploaded for each session. For more on managing your hand database, check out Database Management.
Was this article helpful?
Still need help?
Join our community
Get instant support from experts and fellow players
Join Discord Community