# An IXI project cannot find an input file Check the file reference relative to the saved IXI project. Copy the complete example directory so its referenced inputs remain together. ## Compatibility 8 beta/preview Published guidance with release-applicability limits. Confirm package applicability before following this guide. ## Check the project location 1. Confirm where the IXI project is saved. Read the missing-file indication on Input files. 2. Check the referenced filename and its path relative to that saved project. 3. If you copied only the IXI file, return to the example and copy its complete directory, including the process file, layout and netlist where that example uses them. 4. Use Help > Examples / Templates > Copy to Folder when available. Save the working project and repeat Check and run. ![Studio Input files shows missing-process.ldf with a Missing badge and an Incomplete workflow.](https://static.wixstatic.com/media/31de30_02adf3ccd35641a9a7e00cc1c2d79b6e~mv2.png) A deliberately incorrect process reference is Missing and leaves the workflow Incomplete. Check the filename as well as the badge. ![Studio Input files showing microstrip.gds, process.ldf and microstrip.cir as available.](https://static.wixstatic.com/media/31de30_11951dbd16004b838b273ce5ebc7bc7c~mv2.png) Compare each reference with the working directory. Available is the expected state after the dependency is restored. ## Correct a saved process reference 1. For the supplied microstrip example, keep process.ldf beside microstrip.ixi. If the saved project names a nonexistent missing-process.ldf, open Raw IXI and correct only that filename to process.ldf. 2. Save the IXI, return to Basic > Check and run and wait for the file checks to finish. Run extraction should become available after the dependency is resolved. 3. Run extraction and inspect the new Results/Raw output. The checked candidate completed this recovery with zero reported warnings and parsed errors, matching the original run. Use the actual filename required by your own project. ## Check the result The missing-file issue should be resolved before extraction. A successful file check establishes that the references can be read; inspect the process, geometry and electrical definitions as well before trusting a calculation. ## If the problem remains Provide the exact diagnostic and a generalised example of the relative reference. Review any support bundle before sharing it; a project may contain confidential process or design data. ## Sources and verification details Recorded inputs/builds only. Complete walkthrough and final-package acceptance remain separate. - VAL-005: InductEx 8.0.1 Windows catalog payload. CLI missing-process rejection This CLI check did not exercise GUI controls. Later scoped native candidate evidence is recorded separately as VAL-015; complete GUI and final-package checks remain pending. - VAL-015: InductEx current-source Windows Studio candidate with Core 8.0.1; scenario executable is unversioned. Production GUI controls and normal licensed engine dispatch; current raw result, missing-process correction, GDS PNG export and separate-process restart using a single-tab workaround Bounded native scenario on a frozen source candidate. OS picker input, a clean numerical-results screenshot, mesh refinement, cancellation and final-package acceptance remain unverified. Multi-tab exit selection is held by KB-GUI-006. Computer Use capture remains unresolved. - studio-missing-process: Windows Studio current-source native scenario, 3 November 2026. Illustrates the recorded candidate state. Full GUI article acceptance, numerical refinement and final distributed-package applicability remain pending. - studio-microstrip-inputs: InductEx 8 document view, rendered 3 November 2026. Current-source UI illustration. No calculation or complete GUI walkthrough was performed; final-package applicability remains pending. - inductex:docs/manual/studio_workspace.tex: Documentation and examples; Common problems - inductex:docs/manual/studio_start.tex: First extraction: a microstrip - validation:windows-cli-20261102: VAL-005; scope and limits recorded - capture:studio-ui-20261103T103032: Reviewed current-source document-view images; UI-only scope - validation:studio-native-windows-20261103: VAL-015; current GUI result storage, real licensed extraction/recovery and bounded restart checks - VAL-015 verifies the missing-process badge, disabled run control, saved editor correction and real licensed recovery on the frozen Windows candidate. Do not generalise this reference rule to another tool. Final-package and complete-article checks remain pending. ## Related guides - [Run your first microstrip extraction in Studio](/knowledge-base/inductex-first-microstrip) - [Understand the parallel-plate capacitance example](/knowledge-base/inductex-parallel-plates) - [Use a protected process file and diagnose access failures](/knowledge-base/inductex-protected-process) - [Import an external Gmsh structure and check its result](/knowledge-base/inductex-gmsh-import) - [Model package bonds and check their electrical contacts](/knowledge-base/inductex-package-wirebond)