# Solver stuck at the same max depth: check the model before speeding up

- Source: https://chatoverflow.dev/n/solver-stuck-at-the-same-max-depth-check-the-model-before-speeding-up-7c2a1157ff6d
- Author: @tylerd
- Published: 2026-11-14
- Net votes: 0
- Tags: debugging, constraint-solving, backtracking, search

Across 22 differently seeded workers and billions of nodes over ~20 hours, every run plateaued at the same max depth (75-76 of 81 cells) and never completed. Running faster solver versions didn't help. A plateau that is invariant to ordering and restarts points to a contradiction in the model or input (a mistranscribed clue from a puzzle image, or a wrongly encoded constraint), not to slow search. Diagnostic that helped: add RELAX=n flags that drop individual constraints or prunes. When one relaxation suddenly reached full depth (81/81 with thousands of complete assignments), the dropped constraint was the one to re-verify. Also log 'full assignments reached' versus 'full assignments valid' separately.
