Error and warning message index

This is a lookup table for messages Understand emits during analysis. They appear in the Analysis Log while a project analyzes, and file-scoped errors and warnings are also collected in the Violation Browser's Analysis Errors. Each message carries a severity — Error, Warning, or Note — where a Note usually adds detail to the Error or Warning above it.

This index covers the messages Understand's analysis engine raises itself. It does not try to catalog every per-language syntax error (see the fix below for how C/C++ messages work).

Analysis engine messages

Message	Likely cause	Fix
unable to find file: <path>	A file that was in the project can't be found on disk.	Restore or re-add the file, or refresh the project so the file list matches disk.
unable to find auto include: <path>	An include directory Understand expected (from build capture / auto-detection) is gone.	Re-run your build capture, or add the include directory under fix parse errors.
File '<path>' too large to parse. Change max file size in Project Configuration.	The file exceeds the configured maximum parse size.	Raise the max file size in Project → Configure Project, or exclude the file if it's generated/data.
worker process failed to start: <cmd>	The parser helper executable couldn't be launched (missing binary, blocked by security software, bad path).	Reinstall Understand; confirm antivirus/endpoint tools aren't quarantining the helper.
worker process crashed	A parser helper process died while analyzing a file.	Note which file it was on and see report a crash; the file may be triggering a parser bug.
worker process killed after <n> minutes	A parser helper exceeded the worker-process timeout.	Increase the worker-process timeout in project configuration, or investigate why that translation unit is so slow (huge headers, pathological templates).
server failed to start: <err>	The C/C++ analysis server couldn't start.	Reinstall; confirm the install isn't partial and the helper binaries are present.
invalid internal reference scope: <name> / invalid internal reference: <a> -> <b>	The C/C++ parser produced a reference the database couldn't resolve into a valid scope.	Usually a symptom of an incomplete parse — fix the underlying parse errors first; if it persists on clean-parsing code, report it.

Rust-specific messages

Message	Likely cause	Fix
Rust analysis currently requires a local installation of Rust. Ensure that Rust is installed and that cargo is on the PATH.	cargo was not found on PATH when analyzing a Rust project.	Install Rust and make sure cargo is on the PATH for the account running Understand, then re-analyze.
worker process panicked / worker process crashed	The Rust analysis helper terminated abnormally.	Note the crate/file and see report a crash.
worker process killed after <n> minutes	The Rust helper exceeded its timeout.	Raise the worker-process timeout, or narrow the analysis scope.

C/C++ parser messages (from Clang)

For C and C++, the parse errors and warnings themselves come straight from Clang — Understand forwards Clang's own diagnostic text verbatim. So messages such as 'foo.h' file not found, unknown type name 'X', use of undeclared identifier, or expected ';' are worded exactly as Clang words them, and warnings carry Clang's option in brackets (for example [-Wunused-variable]).

The overwhelmingly common causes are missing include directories and undefined macros, which send the parser down the wrong #ifdef branch. Fix those first — see fix parse errors — rather than chasing individual downstream messages, because one missing header typically produces a cascade of "unknown type" / "undeclared identifier" errors that all clear at once.

AI model-loading errors are separate

Errors like "Failed to load the model file" come from the bundled AI server, not analysis. See that page.