Send safe diagnostics

Send safe diagnostics

When Capture, Save, Open, or Reproduce fails unexpectedly, StatePort can create a small incident report that helps a developer distinguish the symptom, failure mechanism, likely cause, and next repair check.

StatePort sends a report only when you select Send to developers. It does not submit diagnostics in the background.

Send a report

1. Open Settings → Diagnostics.
2. Review the privacy summary.
3. Select Send to developers once.
4. Keep the short report code, such as SP-7K4M-2Q9F, and give that code to the developer helping you.

Some internal, browser, or unexplained reproduction failures offer the same action beside the direct recovery step. When StatePort knows a safe recovery, that recovery remains the primary action and diagnostic submission stays secondary.

A received report is stored privately and deleted after 30 days. It is not linked in the report to your email, license, device, installation, State Card, run, or share. Cloudflare processes ordinary connection information, including the source IP where applicable, to deliver and rate-limit the request. The network connection itself is therefore not identity-free.

If sending is offline, rate-limited, rejected, or temporarily unavailable, StatePort shows a bounded status without displaying the server response, endpoint detail, or raw network error. It does not retry automatically.

Save the same JSON locally

Select Save diagnostic file… to save the same canonical report through a native Save dialog. This action works offline and makes no network request. You can inspect the JSON and send it to a developer through another channel.

The default filename is stateport-diagnostics-YYYYMMDD-HHMMSSZ.json, using the UTC save time. Cancelling creates no file. Open logs folder remains available under Advanced diagnostics for local troubleshooting; do not send the whole logs or application-data folder.

What the report contains

The current file uses the strict version stateport-safe-diagnostics/2.0.0. It includes:

• StatePort version and channel, OS family/version, CPU architecture, and available Electron/Chromium versions;
• one primary typed incident with its operation, visible symptom, failure code, mechanism, fault site, and a bounded event timeline;
• closed evidence facts explaining which required observations were present;
• an evidence-sufficiency status;
• a probable cause and repair code only when all evidence required by the diagnostic catalog is present;
• up to two prior incidents, bounded aggregate context, and omission counts.

If the evidence is incomplete, the report says that the cause is partial or insufficient instead of inventing certainty. The canonical UTF-8 JSON is at most 512 KiB. Unknown fields or malformed incidents are rejected rather than copied into the report.

If StatePort reports success but the shown application state is wrong, use Report incorrect result first. The resulting diagnostic records a verification coverage gap before Send to developers or Save diagnostic file… assembles the report.

What stays out

The report does not include URLs, domains or local file paths; State Cards or their identifiers; project, repository, or environment names; request or response contents; browser storage, profiles or cookies; credentials, tokens, Persona material or protected references; form values, page text, selectors or HTML; source code; email, license, payment, customer, device, installation, Capture, run or share identifiers; raw errors or stack traces; screenshots, video, HAR files, traces or archives. Hashes of excluded identities are also excluded.

Older stateport-safe-diagnostics/1.0.0 files remain readable as legacy local exports. StatePort does not reinterpret them as incident-centered v2 reports.