Skip to content
MachAI Lens Help

Constraint evidence shows "not configured"

Lens shows no error code on screen for this message; E-CONSTRAINT-EVIDENCE-NOT-CONFIGURED is this documentation's name for it. Quote it when you contact the Lens team.

What happened

A Digital Soul constraint evidence card, such as Review Constraint Evidence on the Timing Review tab, shows not configured.

On the card, open the collapsible Constraint Evidence Readiness group. It lists each kind of constraint evidence with a status chip: LOADED, PARTIAL, MISSING FILE (configured, but the file was not found), NOT PARSED (configured, but Lens could not read it), NOT CONFIGURED (no file was given for it), N/A or NOT AVAILABLE. The group is only shown when the card carries readiness information.

Likely cause

The constraint evidence comes from the saved configuration of the active build, and the SDC or report fields it reads have not been filled in there.

Constraint and SDC inputs are optional, and timing analysis does not need them.

Fix

  1. On the Timing Review tab, select Configure… to open the Build Manager.
  2. Select your build, then Modify.
  3. Fill in Constraint / SDC Inputs: specific SDC files, a root folder and a pattern, or a manifest or scenario map.
  4. Optionally, fill in Constraint Validation Reports with your report_clocks, report_generated_clocks and report_exceptions files.
  5. Save. Digital Soul re-reads these inputs on demand, and the card's freshness stamp shows that it was rebuilt.

The Readiness panel lists the next best evidence to load.

Raw SDC and report text never leaves your machine.

Raw SDC text never enters what is sent to Claude. The Review Constraint Evidence action itself never calls Claude at all. A generative explanation of another action may restate the deterministic result of that review, for example that SDC files are configured but missing, but it receives that summary, not the constraints.

If that does not work

If the chip still reads NOT CONFIGURED after you saved the inputs, check that you saved them on the build that is active for the tool you are viewing (Build Manager: Configure, select the build, Set Active), since the card reads the active build's saved configuration; then run the action again, because a card is not updated after it is produced. MISSING FILE or NOT PARSED mean the path was saved: check that the file exists at that path and is the report the slot expects.

If none of this helps, contact the Lens team through the channel you were given with your access to Lens, quote E-CONSTRAINT-EVIDENCE-NOT-CONFIGURED, and include what the screen said.

Still have a question?

Updated 19 October 2026