Troubleshooting
What should I include in a bug report?
Describe a reproducible problem without sharing private account or work data.
Use the Bug Report topic in the website contact form. A useful report explains what happened, what you expected and the smallest set of steps that leads to the problem.
Include these details
- State the Windows version and WorkMimic version if known. Note when the issue started and whether it happens always, sometimes or only once.
- List the steps in order, using the page and control names you selected. Include the exact error wording rather than only saying that it did not work.
- For playback issues, include the source, role if relevant, intensity and enabled events. For recording issues, include the number of completed minutes and the warning shown.
- Submit the message and keep the reference number. If support asks for a screenshot or log, remove sensitive details before sending it in the follow-up.
What to leave out
Do not send passwords, session tokens, activation or reset links, verification codes, card numbers or confidential workplace material. The contact form does not automatically read your app, recordings or desktop diagnostics.
If the issue sends unexpected input, stop playback before collecting details. A plain description of the problem and selected settings is a better first step than repeatedly reproducing it in an important document or transaction.