In this guide1 / 6
Open /feedback from the Help page and sign in with the account you use in Nexlock. Your reports belong to that account. Other members cannot browse them; the owner, Administrators and Moderators can review them in Studio Admin.
Sending feedback creates a private report. It does not publish a roadmap item, create a Discord thread, send an email, or change your account permissions.
A report about an export or Companion issue describes your observation. Submitting it does not rerun the operation or establish that a download, slicer handoff or print succeeded.
Choose Bug report or Suggestion and the affected area: Part Designer, Parts Library, Calibration, Exports, Companion, Account or Other. Enter a short title and the details.
For a problem, add reproduction steps and the expected outcome. The optional environment and Companion version fields help identify the affected setup; Studio records its own version with the report.
Review the text before submitting. Avoid passwords, pairing codes, private project contents and unrelated personal details. Attachments are not accepted in this form.
Submit the report, then keep its reference when discussing the issue with staff. Return to your report list to check progress.
Open one of your reports to read its current status and the staff replies shared with you. Add a follow-up when you have more details or staff asks for information. Every reporter follow-up returns the report to New for staff review, including a report previously marked Fixed or Verified. Internal staff notes are kept separate from this conversation.
If the report changed while you were editing, reload its current state before trying again. Keep a copy of a lengthy unsent reply before reloading. A submission error leaves the work on screen for correction or retry; it does not confirm that a report was saved.
Report status describes the support workflow. It is separate from the Tested status of a printer recipe and does not certify a physical print or connection fit.
| Status | Meaning |
|---|---|
| New | The report is waiting for staff review. |
| Investigating | Staff is examining or reproducing the report. |
| Needs information | Staff needs additional details; check the shared reply. |
| Fixed | Staff has marked the issue addressed; follow the shared instructions to retest. |
| Verified | Staff has recorded that the report has been checked. |
The owner, Administrators and Moderators use Beta feedback to filter or search reports, browse result pages, open a report, and save a response. Set the priority to Low, Normal, High or Blocking according to its impact. A reply shared with the reporter is different from an internal staff note. Check the field label before saving either.
Updates retain a revision history. If another staff member or the reporter changed the report first, reload the latest version and review the new information before retrying. Selecting a priority does not change website access or automatically publish an incident.
- Confirm that you are signed in with the account used to create the report.
- Follow the field limits and the displayed validation message. If a temporary submission limit is reached, wait before retrying.
- Check Service status for an existing incident. A status report may explain a shared problem, but does not replace your private feedback record.
- Keep unsent details until the page confirms a successful save. Closing the page is not a submission.