Skip to content
MachAI Lens Help

Analysis failed

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

What happened

The status on the Timing Review tab reads Analysis failed.

A message comes with it. The message names the stage that failed, what completed before that stage and whether a run was installed, and it gives a diagnostic code. For example:

It failed during the clock-breakdown integrity stage (ImportError). Report parsed: yes. Metrics created: yes. No completed run was installed. Diagnostic code: IMPORT_INTEGRITY_FAILED.

The message carries no file paths or report contents.

KPI cards that show "—" after a run can mean that the run failed, or that it was degraded.

If you used Run All Scenarios, Lens does not show a popup for each scenario. The completion summary is the lasting record: it gives the completed and failed counts, and names each failed scenario with its first-line reason and diagnostic code. A scenario that started and then failed counts as failed, not completed.

Likely cause

One stage of the analysis failed, and the message names it. In the example above, the code IMPORT_INTEGRITY_FAILED comes with a failure during the clock-breakdown integrity stage.

The seven codes, one per stage of the import, in the order the stages run:

Code Stage that failed
IMPORT_SELECT_FAILED report selection: choosing which report files to read for the scenario
IMPORT_PARSE_FAILED report parsing: reading the timing report
IMPORT_LONGNET_FAILED long-net analysis: the net-segment breakdown of the top paths
IMPORT_METRICS_FAILED metrics creation: building the per-clock figures from the parsed paths
IMPORT_INTEGRITY_FAILED clock-breakdown integrity: the parsed clocks and the breakdown table did not agree
IMPORT_RUN_CREATE_FAILED run creation: saving the run under the build
IMPORT_PERSIST_FAILED result persistence: writing the result files

A failure in a stage before IMPORT_RUN_CREATE_FAILED means nothing was saved; the message also says whether the report parsed and whether metrics were created before the failure. The message gives the failing stage and the type of the error, never the error's own text, because that text could contain a file path or report content.

A degraded run is a different outcome. In a degraded run the report imported, but part of the analysis could not be produced: for example, timing paths exist but no clock references could be read. A degraded run shows warnings in the alerts list, beside the results that did import, and never also reports success.

Fix

Check the status line and the alerts list, to see whether the run failed or was degraded.

The full technical detail, including the traceback, is printed to the terminal window you started Lens from (see Install Lens); Lens writes it nowhere else. Keep that window open while you work.

To recover:

  1. The results area still shows your previous successful run, if there was one; a failed run never replaces it.
  2. For IMPORT_SELECT_FAILED or IMPORT_PARSE_FAILED, open Configure and check that the scenario's report files exist, are readable and are the right kind of report in the right slot (a setup report in the setup slot, a hold report in the hold slot); then run the scenario again.
  3. For IMPORT_RUN_CREATE_FAILED or IMPORT_PERSIST_FAILED, check that Lens can write to its data folder, ~/.chipcopilot/ (disk space, permissions), then run again.
  4. For the other codes, run the scenario once more; if it fails the same way, copy the message and the terminal output and report it.

If that does not work

Report the problem, and quote the diagnostic code from the message. The code is stable, so it can be searched for.

Send it to the Lens team through the channel you were given with your access to Lens, with the terminal output from the failed run.

Still have a question?

Updated 19 October 2026