If RapidDox fails partway through processing a file, the support team can usually pinpoint the cause from your debug log. The steps below turn on detailed logging, reproduce the issue so it gets captured, and send the resulting rapiddox.log file to support.
Steps
- Open the desktop app's Settings tab and turn on Enable Error Logging.
- Re-run the action that failed — open the same file and process it again. RapidDox writes detailed diagnostics to
rapiddox.logwhile logging is on. - Locate the log file on disk — see Log file location below.
- Send the file to support — open a ticket on the RapidDox support portaland attach
rapiddox.log. Include a short description of what you were doing when the error happened. - Once you've sent the file, return to Settings and turn Enable Error Logging off again.
Log file location
The log is written to a fixed path that depends on your operating system:
| OS | Path |
|---|---|
| Windows | C:\Users\<username>\AppData\Local\Rapiddox\rapiddox.log |
| macOS | /Users/<username>/Library/Preferences/Rapiddox/rapiddox.log |
Replace <username> with your OS account name. The log rotates after roughly 10 MB — older copies are kept next to the main file as compressed .gz archives; if support asks for "the last few runs" attach those too.
Turn it back off when done
Leave Error Logging off in normal use. With it on, RapidDox writes detailed debug records on every action, which slows extraction down. Re-enable it only when you need to capture another bug for support.
Related: Desktop App Settings.