What steps will reproduce the problem? 1. Load and initial state and use a solver to solve it. Solver.hasFlaws() correctly returns false. 2. Add something (for example, parse some new NDDL). 3. Solver.hasFlaws() INCORRECTLY return false.

The problem is that the solver has an internal variable m_noFlawsFound that has no way of knowing that things have changed (so it becomes stale).

An obvious solution is to remove that variable, and force the code to recheck every time hasFlaws() is called - ie call allocateNewDecisionPoint(). However, this doesn't feel like a method that should have side effects. A discussion is currently under way on the developers mailing list....

Addressed in r6751 by adding a FlawManager::noMoreFlaws method and various implementations.