Avanti diagnostic reports use the filename pattern <base>_YYYYMMDD_HHMMSSmmm_<reason>.cra, where <base> is the configuration filename without its final extension.  For example, a report produced by the Halt command at 14:30:12.347 on September 6, 2026 for Alpha01.cfg is named Alpha01_20260906_143012347_halt.cra.  The timestamp is the host's local time, including milliseconds.  The final short reason identifies the internal condition that requested the report.

The report is written in the same folder as the configuration file.  Its contents are gzip-compressed even though the file retains the Avanti-specific .cra extension.  Each timestamped report is a separate file; creating a later report does not normally replace an earlier one.

Avanti may create a report after a fatal emulator failure, a related OpenVMS failure, or another internal diagnostic condition.  Using Halt on the Avanti Control Icon always creates a report whose reason is halt; that file records the requested diagnostic state and does not by itself mean that Avanti crashed.

A report includes the failure description, exact Avanti build, host operating-system and processor details, the complete configuration text, exception information, and detailed emulator and device state.  Licensed builds can also include the license serial, generation, customer, and license comments.  Configuration values and diagnostic state can expose customer names, host paths, network or device details, and other operational information.

Treat .cra files as confidential diagnostic data.  Keep the original file unchanged, review its handling under your organization's security policy, and provide it only through the support channel agreed with Migration Specialties.  Do not post a crash report to a public forum.  Unless support asks otherwise, send the original compressed .cra file together with the configuration and log files described under Problem Submission; you do not need to rename or decompress it.