For six weeks the model does exactly what it is supposed to do. Then a colleague changes one dimension for a customer variant, hits Update, and watches the feature tree turn red: two features broken, a sketch pointing at an edge that no longer exists, and a component Inventor can no longer find. The change itself was five minutes of work. The rest of the afternoon is spent clearing up the wreckage.
The cause had been sitting in the model for weeks, invisible. Suppressed features are a silent risk in Inventor: they do nothing, so they attract no attention, but they are not gone either. The same goes for references that have quietly been broken: the model looks healthy until someone pulls on it. In this article we dig into that one category of problems: how suppressed features, suppressed components and broken references come about, how you hunt them down systematically, and when to choose between repairing and deleting for good, with a toolbox like Thundercad for the cleanup work.
Suppressed is not gone
A suppressed feature still sits right there in the tree. Inventor does not compute it, but it keeps everything: the sketch, the dimensions, the references to faces and edges. If it ever gets switched back on, all that stored work suddenly has to agree with a model that has moved on ten changes since. The longer a feature stays suppressed, the bigger the chance it breaks at the worst possible moment: during the rush change, right before release, on the day the experienced colleague is off.
With suppressed components in an assembly a second layer appears: the bill of materials. Whether a suppressed component is counted depends on how the assembly and the BOM view in use are configured, and that unpredictability is exactly the risk. One person reads the list with the component in it, the other without. The fitter who is one set of brackets short only notices during assembly. We wrote about that kind of surprise earlier in Five BOM errors that only show up on the shop floor.
Mass and centre of gravity also only count what is active. A suppressed cutout or a suppressed lightening pattern quietly puts a couple of kilos of difference between model and reality, without anyone ever seeing an error message.
How sick features and dangling references are born
Almost always it starts with good intentions under time pressure. Three routes keep coming back:
- The quick fix. A feature breaks during a change, the deadline looms, so: suppress it and solve it later. Except later never comes, because a suppressed feature no longer raises an error.
- The variant without a plan. Switching features on and off as a cheap way to create versions. It works, until nobody remembers which combination belongs to which version.
- Inherited work. The model was copied from an earlier project, including features that made sense there and not here. Switching them off is faster than understanding them, so they stay.
Broken references have an origin story of their own. Inside a part: a sketch projects an edge, a later change makes that edge disappear, and the sketch grabs at thin air. Between files: a part gets renamed or moved outside Inventor or Vault, and the assembly or the derived copy can no longer find its source. In both cases the parametric behaviour is gone: the model no longer responds predictably to a change, and every edit becomes a gamble.
How to track them down systematically
Waiting until things go wrong is a strategy too, just an expensive one. Better is a fixed sweep, for example before a model heads for release:
- Work in a copy or a checked-out version, so you can experiment freely.
- Unsuppress everything and let the model compute fully. Errors that kept quiet for months now show up on your screen instead of later at work preparation.
- Walk the browser for error and warning markers, inside the parts as well, and note what you find.
- Check the BOM view of the assembly: are there suppressed components in it, and do they belong there?
- Open the matching drawing and look for dimensions that have lost their reference.
- Decide per find: repair, delete for good, or deliberately leave suppressed with the reason attached.
A sweep like this costs an hour and prevents the afternoon of wreckage from the first paragraph. With tooling that finds the clutter for you, it goes faster still.
Try 30 days freeRepair or delete for good
Not everything you find deserves the same treatment. A workable rule of thumb: if the feature serves a purpose in a version or a customer option, you repair it and record why it exists. If it is an experiment, an old option that will never return or a duplicate operation, it goes for good. Half work, a broken feature left suppressed, is the worst outcome: the problem stays, only the warning disappears.
For a broken sketch reference, repairing usually means: open the sketch, reattach the loose projection or dimension to existing geometry and check whether the design intent still holds. Broken file references you solve at the right level: restore the link to the moved file, and agree that renaming and moving happens through Vault or the project file from now on, not through the file explorer.
For the leftover category, abandoned sketches, unused work planes and imported junk geometry, there is no need to click feature by feature. With Model Cleaner from Thundercad you clear leftover geometry and clutter in one pass, so that gone for good really means gone and the file does what the tree promises again.
One item from a bigger whole
This sweep is deliberately narrow: one category of problems, tackled thoroughly. Preparing a model for production also means looking at naming, materials, iProperties and the drawing set; the full sequence for that is in Cleaning up Inventor models before production: the complete checklist. The difference: the checklist makes sure you skip nothing, this deep dive makes sure that on this one item you know what to look for and why.
The real win, in the end, sits in behaviour: repair at the moment something breaks, instead of suppressing it for later. On the day itself that feels like a delay, and it is the cheapest repair you will ever carry out.
Frequently asked questions
Does a suppressed component count in the bill of materials?
Sometimes it does, sometimes it does not: it depends on how the assembly and the BOM view in use are configured. Which is exactly why the only safe route is: check the BOM view itself before release and decide deliberately, per suppressed component, whether it belongs in the list.
Is it ever fine to leave a feature suppressed on purpose?
Yes, as long as it is a choice and not a postponement. A customer option or version driven by a suppressed feature is fine, provided the reason is recorded, for example in the feature name. A broken feature left suppressed "until there is time" is not a choice but technical debt.
Can I clean up this kind of clutter in bulk?
The judging part, no: choosing between repairing and deleting remains human work. The cleanup itself, yes: Model Cleaner removes leftover geometry and clutter from your files in one action. You can try it without obligation in the free trial month of Thundercad.