Export a selected Studio support bundle and review its contents

Choose the archive for the task

Use Help > Support Bundle when you want selected saved documents, diagnostics and explicitly chosen output/log files in a local ZIP. Exporting creates the file; it does not send it to support.

A support archive is not automatically a portable calculation project. The checked archive renames copied documents with prefixes such as document-files/doc-03-strip.ixi while the original project still refers to process.ldf and strip.cir. The related calculation-record guide preserves a separate runnable hierarchy and verifies a fresh rerun.

If you want to follow this with known inputs, the complete teaching ZIP contains strip.ixi, process.ldf and strip.cir. The portable-record instructions in its README are an optional separate route; the native Support Bundle steps below do not require Python or PowerShell.

Select only the evidence you intend to share

1. Open the intended saved project and the dependencies you need. If unsaved edits are required to reproduce the problem, save a deliberate working copy first. Review dirty/unsaved flags; the native exporter copies on-disk bytes, not the editor buffer.
2. Open Help > Support Bundle. Check only the relevant open documents. Uncheck unrelated designs and never select an actual licence file, credential or process passkey for inclusion.
3. Choose whether Copy selected saved open-document files is needed. With it off, selected documents still contribute their diagnostic/open-document summaries. The checked minimal selection includes one project and one explicitly added log.
4. Use Add output/log files for the current calculation output or other evidence. Adding the same path twice is deduplicated. A document diagnostic summary does not replace the extraction output log. Review the actual files you select.

Include saved source only after reviewing its state

For the complete teaching input selection, choose all three saved files and enable Copy selected saved open-document files. The checked archive contains byte-identical on-disk copies. A deliberate unsaved editor marker did not appear in those copies or any other archive member.

The dirty flag is therefore a practical warning about reproducibility: the bundle can contain an earlier saved source than the text visible in the editor. Saving a suitable copy is a separate action; export does not save it for you.

Viewer snapshots apply to selected snapshot-capable GDS/Mesh documents. That option is unavailable for this text-only selection. Snapshot generation and its remaining platform branches are not qualified by this support scenario.

Review the generated reports and raw copies

The native checks confirm limited prefix redaction, retention of text outside those prefixes, and byte-for-byte copying of the explicit raw logs. Turning saved-file copying off does not make the remaining reports or logs anonymous. Read the ZIP contents before deciding what to share.

The maintained extra-file policy skips missing files and files larger than 64 MiB with manifest notes; it is not a cap on the entire archive. The two small-file selections were exercised here, while the exact size boundary was not requalified in this walkthrough. Inspect skip messages rather than accepting Exported as proof that every selected file was included.

Export, cancel or recover from a locked destination

1. Choose Export ZIP and an appropriate writable local destination. Cancel leaves the options available; the checked cancelled selection created no archive.
2. After success, open the ZIP locally and review the manifest, generated reports and copied files. It can include design information and licence-status metadata. Creating the archive is not permission to transmit every member.
3. If replacement fails because a target archive is open or locked, read the new error, release the lock or choose a suitable new destination, and retry. In the checked real locked-file failure, the previous archive stayed byte-identical; after unlocking, retry included the changed explicit log.
4. Confirm the new archive and content, not merely the presence of an earlier ZIP. Keep a selected support archive separate from a portable calculation record when you need both.

Understand the checked boundary

VAL-034 has 25 independent checks on the frozen current-source Windows candidate, including normal licensed extraction, native selection/copy options, raw file deduplication, saved/unsaved handling, Cancel and a real locked-target failure/retry. The file paths were supplied at the production picker boundary; physical OS picker operation and final distributed-package checks remain pending.

The supplied input ZIP is the same complete teaching project used for the separate portable-record checks, VAL-035. No real generated support ZIP is offered as a public teaching download because its runtime and raw reports can contain local/private information.