Skip to main content

Overview

Rebuild errors, broken external references, mate conflicts, and corrupted feature trees are routine in CAD work — and routinely time-consuming, because the error message rarely points straight at the cause. An over-defined sketch, a missing mate reference, or a broken link after a file move can each take longer to trace than to fix. Describe what you’re seeing — the error message, what changed recently, what you expected instead — and Nexus works through the likely causes the way an experienced user would, then applies the fix on your confirmation.

What Nexus can help with

  • Rebuild errors — Diagnose failed features: over-defined or under-defined sketches, missing geometry references, invalid feature parameters.
  • Broken external references — Repair dangling links after a file was renamed, moved, or a referenced part changed shape.
  • Assembly mate and constraint errors — Identify which mate is over-constraining or conflicting, and why, in assemblies with many components.
  • Corrupted or unstable feature trees — Isolate which feature in a long history is the actual source of instability, not just the first one flagged.
  • Drawing errors after a model change — Fix out-of-date or broken views, dangling dimensions, and missing annotations after the underlying model changes.
  • Import and translation errors — Diagnose why an imported STEP or IGES file failed to translate cleanly or won’t open.

Example prompts

The debugging mindset

The most effective error-fixing prompts follow the describe symptoms rule from the Prompting Guide:
  1. State what happened — the exact error message, the feature or mate it’s attached to, and when it started.
  2. State what you expected — what a correct rebuild or result should look like.
  3. State what changed recently — the edit, import, or rename that likely triggered it, so Nexus doesn’t have to guess at the trigger.
Here’s an example that does all three:

Tips for error-fixing prompts

  • Paste the exact error message — the precise wording usually names the feature, mate, or entity Nexus needs to locate the problem, rather than a paraphrase.
  • Say what changed recently — a rename, a suppressed feature, an edited dimension. Most CAD errors are triggered by a specific prior change, and naming it narrows the diagnosis immediately.
  • Distinguish the trigger from the symptom — in assemblies and long feature trees, the first error shown often isn’t the root cause. Ask Nexus to trace back to the actual source.
  • State constraints on the fix — “don’t change the outer profile”, “this feature needs to stay suppressed for the lightweight configuration” — so the fix doesn’t solve one problem by creating another.
  • Ask for the explanation, not just the fix — understanding why an error happened prevents the same class of error on the next model.