Compatibility
7.x historical cases / 8 draft guidance
Package applicability is under review; follow the stated version and platform limits.

Find the first failing stage

  1. Open the current run summary and sol.txt. Check whether layout processing, label discovery and meshing succeeded before the engine was invoked.
  2. If no ports/labels were found, check the selected cell, hierarchy and process text-layer setup.
  3. If TetraHenry® did not run, resolve the preceding geometry, meshing, executable or licence diagnostic before looking for its output file.
  4. Run each simultaneous job in a separate writable working directory. Check timestamps so old results are not confused with the failed run.

Do not manufacture the missing file

Creating an empty i.txt or copying an older output cannot recover the missing calculation. Collect the first error, exact versions and a minimal redistributable project if the failure persists.

Support history contains more than one possible cause. Shared-directory interference was proposed in one thread but not confirmed as the explanation for every missing-file report.

Completion is not the success criterion

The checked 8.0.1 missing-process run printed both Not successful and Job finished, and exited with code 1. Treat the earliest error and exit status as the outcome; the words Job finished alone do not prove a successful extraction.

Sources and verification details

Recorded inputs/builds only. Complete walkthrough and final-package acceptance remain separate.

  • support:SUP-006 · Generalised editorial finding; outcome qualification retained
  • inductex:docs/manual/ix_output.tex · Solution output
  • inductex:docs/manual/studio_results.tex · Run summary and artifacts
  • inductex:docs/manual/ix_ports.tex · Terminal labels and cell hierarchy
  • validation:windows-cli-20261102 · VAL-005 failed-run completion wording; missing-i.txt causes were not reproduced
  • Support history informed this draft. Current-source guidance has been checked; a fresh walkthrough on the intended distributed release and product-owner review remain pending.
Read MarkdownRead structured articleBrowse all guides