Skip to content
MachAI Lens Help

A scenario is reported incomplete

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

What happened

Lens reported a scenario as incomplete and did not analyse it. It refused the run and reported why.

Lens does this instead of saving the scenario with the missing side recorded as WNS 0.0 and 0 violations, which would read as clean.

Likely cause

The scenario's configured setup pattern or hold pattern matched no file, while the other pattern did.

A PrimeTime scenario needs both a setup report and a hold report, unless the project's one-sided opt-in is on. Fusion Compiler analysis works with either report on its own.

Fix

If your flow writes both reports, fix the pattern that matched nothing:

  1. On the Timing Review tab, select Configure… to open the Build Manager.
  2. Select the build, then Modify to open the Timing Analysis Configuration dialog.
  3. Under PrimeTime Inputs, correct the SETUP pattern (for example *_max_timing_GBA.rpt* or *_max_timing_PBA.rpt*) or the HOLD pattern (for example *_min_timing_GBA.rpt* or *_min_timing_PBA.rpt*).
  4. Save.

After saving, click Rescan (the Scan / Detect Scenarios button) so Lens finds the files under the corrected pattern, then run the scenario again. The saved results of other scenarios are kept.

If your flow genuinely writes only one of the two reports, turn on the one-sided opt-in instead (Analyse a scenario that has only a setup or only a hold report), in Settings under Data Sources. It is off by default, and it applies to the open project only.

With the opt-in on, the side that has no report is shown as not measured, with a dash (—) in its cells, whether the build is PrimeTime or Cadence; it is never shown as clean or as zero violations.

A project with a Cadence (Tempus or Innovus) source has this setting turned on once, automatically, because Cadence writes one timing report per run. If you turn it off afterwards, it stays off.

If that does not work

The MACHAI_ALLOW_ONE_SIDED variable overrides the project setting for a whole session. When the variable is what decided, the refusal dialog says so and names it.

It is set in the terminal before starting Lens, for example export MACHAI_ALLOW_ONE_SIDED=1 on macOS or Linux; 1, true, yes or on allow one-sided runs and any other value forbids them, whatever the project setting says. To go back to the project setting, clear it with unset MACHAI_ALLOW_ONE_SIDED and start Lens again. Normal use needs neither: the Settings tick-box is the intended control.

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

Still have a question?

Updated 19 October 2026