Send a report
Sign in to the Console and choose Report an issue in the header. This action is available across provider, renter, account and administration screens, including during approval, onboarding and Terms problems. Reporting does not grant access to other restricted features. You do not need a tracker account.
Enter a short Issue title and describe What happened? Include what you were doing and what you expected. Expand Technical details included to preview the browser diagnostics, then choose Send report.
Your unsent text stays available through ordinary Console navigation and temporary submission failures. Closing the report dialog preserves the draft. Signing out or switching accounts clears it; reloading or closing the browser also loses the memory-only draft.
Information included
Safe technical details help investigate the issue: application versions, deployment information, timestamps, your account reference, relevant capabilities, a safe screen label, browser details, recent request results and timings, request references, and safe error locations.
Support can use request references and timestamps to find related backend activity in restricted operational logs. Raw backend logs and private log-service links are not attached to the issue tracker.
Recent diagnostic history covers up to 40 events over 10 minutes. Browser history stays in memory and is kept separate between accounts. Live connection and reconnection categories may be included; live event contents are excluded. The server adds verified identity, deployment and recent failed-request details. Browser-supplied details are treated as unverified.
When relevant, the server may include your own rental or workspace, listing, cluster, node or operation reference, its saved state and observation timestamps. An old or unknown observation is not a new health check. Submitting a report does not inspect your workload or run remote infrastructure checks.
Privacy boundaries
Do not paste confidential material, passwords, tokens, private keys, payment details, or workload contents. User-written text receives best-effort redaction, which cannot catch every possible secret.
Automatic collection excludes credentials, cookies, authorization headers, browser storage, request and response bodies, files and workload contents, terminal output, screenshots, arbitrary logs, raw exception messages, kubeconfigs, node join tokens, network secrets and signed link parameters. Request paths omit query strings and private dynamic segments. Reports do not include another account's private resources.
References and delivery
After saving, you receive a stable CC- report reference. Keep it if you contact support. Open the reporting dialog's Your recent reports to inspect your latest five submissions.
| Status | Meaning |
|---|---|
| Saved for delivery | Your report is stored and queued for automatic delivery. This does not yet confirm delivery. |
| Delivery being checked | Your report is stored; an uncertain delivery is being checked to avoid creating another copy. |
| Sent | Delivery to the issue tracker is confirmed. |
| Delivery needs attention | Your report is stored, but delivery could not be confirmed automatically. Keep the reference for support. |
If you report the same issue again within the duplicate window, the Console shows your existing reference. Retrying after a network failure also preserves the original submission. A temporary reporting outage keeps your draft available so you can try again.
Limits and retention
The defaults are 5 reports per hour, 20 per day, and a 24-hour duplicate window, per authenticated account. Titles accept 3–160 characters; descriptions accept 10–8,000. If you reach a limit, wait before trying again.
Finished, resolved application report records are normally retained for 90 days. Unresolved delivery records are preserved for investigation. Recent request diagnostics expire after 10 minutes. Copies delivered to the issue tracker follow its separate retention policy; removing an application record does not remove the tracker issue.
Restricted production operational logs follow a separate policy of at least one year. This does not extend browser diagnostic history or application report-record retention, and it does not restore logs that were already deleted.