You delete one face, hit rebuild, and the tree lights up: 38 errors, half the features flagged, the model unrecognizable. The instinct is to start clicking through every red mark from the bottom up. That instinct is what turns a 15-minute fix into an afternoon.
Why one change produces dozens of errors
SolidWorks builds a part as a chain of parent-child dependencies. A sketch is a child of the plane or face it was drawn on. A fillet is a child of the edges it rounds. A pattern is a child of the feature it repeats.
When a parent disappears, every descendant loses its reference at once. The tree reports all of them, but they are not 38 independent problems. They are one problem reported 38 times.
Behind this sits the topological naming problem: SolidWorks identifies faces and edges by internal names such as Face<7>. Change the geometry upstream and the numbering shifts, so a feature that referenced Face<7> now points at a different face — or at nothing.
The order of operations that works
- Do not fix anything yet. Open What's Wrong (right-click the part name at the top of the tree). Read the full list once before touching the model.
- Find the topmost error in the tree. Not the first one you notice — the one highest up the feature list. That is the parent.
- Fix only that one. Resolve its missing reference and nothing else.
-
Force a full rebuild with
Ctrl+Q, notCtrl+B. A standard rebuild only reprocesses features it thinks are dirty; a forced rebuild reprocesses everything and gives you an honest error count. - Re-read the list. In most cases the count collapses from 38 to two or three genuine errors. Repeat from step 2.
The discipline is the whole technique: one fix, one forced rebuild, one re-read. Fixing four errors before rebuilding means you cannot tell which fix worked.
Distinguishing errors from warnings
The tree uses two markers and they mean different things:
- Red error — the feature failed to build. The geometry is not there.
- Yellow warning — the feature built, but a reference is dangling or a relation is over-defined. The geometry exists and may look right, which is exactly why these get ignored until they cause a problem downstream.
Clear the red first. Then come back for the yellow, because yellow warnings are what produce the next cascade three weeks later.
Fixing the reference itself
Once you have isolated the parent, you have three options, in order of preference:
- Redirect the reference. Right-click the failed feature and choose Edit Feature, then reselect the face or edge. Fastest when the replacement geometry is obvious.
- Re-anchor to stable geometry. If the feature referenced a face that keeps moving, rebuild its sketch against an origin plane instead. Slower now, permanent later.
- Roll back and reorder. Drag the rollback bar above the problem feature and move it earlier in the tree, before the geometry it depends on became unstable.
How to stop the cascade happening again
- Sketch to the origin and to planes, not to model faces, wherever the design intent allows it. Planes never get renumbered.
- Never reference a fillet face. Fillets are the most frequently edited features in any part, and every reference to one is a future error.
- Put cosmetic features last. Fillets, chamfers and drafts belong at the bottom of the tree so nothing structural depends on them.
- Use Display/Delete Relations monthly on parts you inherit, filtering for dangling relations before they become somebody's 38-error morning.
When you still cannot find the parent
If the tree gives you nothing useful, stop describing the symptom in your own words. Copy the literal error text from What's Wrong, note the feature type, what you changed immediately before the failure, and whether the part came from an import or a translated file. A structured description of the exact failure gets you a root cause; "my model broke" gets you a list of generic suggestions.
The full walkthrough of this case — one deleted face, 38 errors, resolved step by step — along with 12 field playbooks for broken references, slow assemblies and sheet metal failures, is in The AI Copilot for Mechanical Designers.