Feedback and progress tracking¶
Feedback at the bottom of the sidebar submits problems to technical support. Submission, attachment uploads and progress queries require Internet access. Draft editing, local history and screenshot previews work offline.
Description and attachments¶
Choose a feedback type and describe the problem, reproduction steps and expected result. The description accepts up to 30000 characters; contact information is optional and limited to 500 characters.
Include system information is enabled by default. It collects the application version, operating system, CPU, RAM, GPU model and memory, graphics driver and main application dependency versions without starting training engines. It does not actively collect machine codes, license keys, usernames or datasets.
Include training logs is enabled by default. It includes the current console and existing engine.log, results.csv and training_metrics.jsonl from the selected experiment. The most recently registered experiment is selected by default; Current console log only can also be selected. Only the latest approximately 256 KB of each file is captured. Original files remain unchanged; models and training images are not uploaded.
Common local paths and credentials are automatically hidden in logs, but not every sensitive value can be recognized. Inspect the preview before submitting, and uncheck logs or system information if unnecessary.
Select local images or paste screenshots from the clipboard. Double-click the attachment list to preview, or remove an attachment. Up to 4 images are converted to PNG; images with a long edge above 4096 pixels are reduced, and each processed image is limited to 4 MB.
Preview and submission¶
Click Preview and submit feedback, inspect contact details, system information, log contents and the screenshot list, then click Confirm submission. Cancelling the preview uploads nothing to the feedback platform; the draft and preview record remain local.
Attachments upload before feedback is created. Visibility of the description and attachments depends on the feedback platform's permissions; this is not a private chat. The form is locked during submission to prevent changes. Cancellation can be requested, but the current network request must finish first.
History and progress¶
History contains only this computer's records: feedback number, submission status, last sync time, description and synchronized replies. Drafts and records are stored in the current user's local application data directory and persist after closing the software.
After successful submission, Check progress retrieves the corresponding feedback's status and replies. States include Received, In progress, Closed and Rejected. Closed does not mean the software verified that the problem was solved. Technical support handles feedback and replies; the client does not generate handling conclusions automatically.
At most the first 100 replies are retrieved. Contact technical support for the complete record.
Records with failed uploads or definite submission failures can be reviewed and retried. Successfully uploaded attachments are reused rather than uploaded again.
If creating feedback times out, loses its connection or returns an ambiguous response, the record shows Needs verification and cannot be blindly resubmitted. Contact technical support to confirm the outcome. If it was created, use Link feedback number to enter the number provided by support; the software verifies that it belongs to this local feedback before linking it and querying progress.
Exit is blocked while a feedback operation is running. Cancel or wait for completion before closing. A normal exit saves the current draft.