Export safe diagnostics

Before you begin

• The affected build/host version and a clear failed step or original operation reference.
• An eligible installed Diagnostics surface for local checks/export; otherwise prepare a short redacted text description.
• A local output folder you can write to.

Follow the steps

1. Record the problem precisely

   Note Vector OS build, OS/architecture, host/plugin versions, failed step and safe error/operation references. Include whether the action may already have been dispatched.

   Checkpoint: The issue can be located without passwords, email codes, tokens, raw prompts or a complete model.

2. Run the available read-only checks

   In Settings > Diagnostics/Help, use Run checks if this build exposes it. Read the named categories and any omitted/unreadable source.

   Checkpoint: The report diagnoses state without editing the CAD model or replaying a failed operation.

3. Preview the selected categories

   Review the manifest and redactions before export. Exclude credentials, pairing secrets, prompts, model content and unnecessary full local paths.

   Checkpoint: You can see what will be included and what was omitted; an unreadable log is stated rather than silently replaced.

4. Export to your chosen local folder

   Choose Export and grant a destination. Inspect the resulting bundle/reference and redaction policy. Cancel if the preview is not safe.

   Checkpoint: A local artifact is saved with an identified result. Export alone has not uploaded data or created a support case.

5. Choose the actual support destination

   Open Support and read whether the route is email/contact or an authenticated case flow. Share only the selected redacted information you intend to submit.

   Checkpoint: The destination and any additional upload are explicit; clicking a guide link does not attach diagnostics.

6. Use supported attachment items when enabled

   For authenticated support, select at most three distinct PDF, PNG, JPEG, UTF-8 text or JSON items, each 1 byte to 10 MiB and 20 MiB total. PDFs are at most 20 pages; images at most 16 megapixels.

   Checkpoint: Only selected valid items are submitted. ZIP, CAD/BIM files, executables and remote-URL attachments are excluded; JSON must use the redacted diagnostic schema.

Check the result

• You have a reviewable local diagnostic result and a separate deliberate sharing decision.
• If a support submission becomes available, its server-confirmed case/reference is distinct from local export.

If something goes wrong

• A log cannot be read or export fails.

  Keep the stated omission and error. Choose an accessible destination or prepare the safe version/error facts manually; do not elevate or collect unrelated folders.

  Resume from: A clearly identified new or resumed local export.

• A selected attachment is too large, unsupported or fails verification.

  Keep the draft and valid selections. Remove/replace the failing item deliberately; do not silently omit it and claim the original evidence was sent.

  Resume from: Reviewed supported selections.

• A case submission response is lost.

  Keep the original case/request reference and reread its status when that service is available. Do not create duplicate cases or upload the same evidence repeatedly.

  Resume from: Original case outcome.

Continue with a related guide

• Current support destination
• Include the original unknown-operation reference
• Privacy boundaries
• Model context uses different limits