InductEx® finishes but does not create a back-annotated deck

Recognise the checked case

Extraction can finish successfully while warning that no back-annotation was performed. The reproduced warning is: Back-annotate command has moved to the main IXI file "$CONTROL" block. Ignored in netlist.

The older manual describes the command in the netlist .control block. The checked 8.0.1 Windows runtime ignores that location. This answer records the tested recovery; it does not assign the same behaviour to every earlier release.

Move the request to the project

1. Work on a complete project copy in a fresh writable folder. Keep the existing target JoSIM/SPICE template beside the IXI file.
2. Remove the legacy BACK-ANNOTATE request from the extraction netlist .control block. Preserve unrelated control statements.
3. Add the following top-level block to the IXI file, using the actual template filename.
4. Keep an explicit target element mapping on each extraction branch to be transferred. For the linked example, L1 1 2 3.9e-12 [LTRANSFER] maps extraction L1 onto simulation LTRANSFER.
5. Run extraction again, inspect warnings and locate the new annotated deck in the run output directory. Compare the mapped value with the new solution before simulation.

$CONTROL
  BACK-ANNOTATE "transfer.cir"
$END

Check the result and remaining causes

For the checked local template transfer.cir, output/transfer_annotated.cir was created and the original template was unchanged. Its LTRANSFER value agreed with the extraction solution at printed precision; JoSIM then ran that new deck successfully.

If the file is still missing, verify the template exists relative to the IXI project, the requested target name is correct and the output directory is writable. Read the actual licence warning too: current source allows automatic back-annotation for SUPER/QUANTUM, and can skip it when that entitlement is unavailable.

If a new deck exists but an element was not updated, inspect its bracket mapping and the target element name. A successful extraction does not establish that every requested template target was replaced. Use fresh output names so an earlier annotated deck cannot be mistaken for a new result.

Retain version/build identity, the generalised diagnostic, extraction circuit, IXI control block and a shareable template when escalating. Exclude licence details and private fabrication/customer files.