Troubleshooting
| What you see | What to do |
|---|---|
| Run is unavailable | Save a profile, return to Workspace, select it under PROFILE, and check that VIEW FILES contains supported queued documents. Wait for any current selection or run to finish. |
| Documents are missing from the queue | Check the excluded list, file extensions, folder permissions, and subfolders. Try Add Files for a specific file. |
| A profile is absent from the dropdown | Confirm Profile saved successfully, then return to Workspace. The current profile list loads JSON profiles; older profile formats are not listed. Recreate an older profile through the editor or seek help converting it. |
| Save failed: or ERROR in Profiles | Keep the editor open, read the message, correct the validation or folder-access problem, and Save again. Do not assume a failed save persisted your changes. |
| ERR / engine unavailable in Settings or the bottom status bar | Read the detail under anonymize in Settings. Restart after repairing or reinstalling the application's matching engine through your distributor or administrator. An OK probe only establishes engine availability, not that a document will process successfully. |
| Failed job or Workspace ERROR | Read and record the displayed message before another run. Check access to inputs, the saved profile, and the output folder. Correct the reported problem and use Retry, or rebuild the queue if the files/profile changed location. |
| Folder or permission error | Choose an existing writable OUTPUT FOLDER in Settings and confirm the OUTPUT path in Workspace. Check input files are still readable. |
| A run was interrupted by closing the app or a crash | Reopen Workspace. Older unfinished jobs are marked Failed; they do not automatically resume. Check for partial outputs before retrying. |
| Open or Reveal does nothing | Use your file browser to open the output folder shown for a new run, or the folder you used for that older job. Check that the file still exists and a suitable default application is installed. These actions may fail without an on-screen error. |
| Local AI does not work | Check your Ollama service and the actual installed model, or disable LOCAL AI and retry without that optional layer. Do not rely on the sample Ollama OK row. |
| Processing completes but sensitive information remains | Do not share the output. Check the selected profile and supplied values, consider the OCR request for scanned content, and process the source again. If the engine cannot handle the content, use another approved workflow rather than assuming success. |
A failed batch can still have produced some files, and Open / Reveal may be available for those outputs. Check the destination manually even when those buttons are absent: an interrupted operation may leave files that were not recorded as complete. Do not treat partial output as reviewed or safe.
When asking for help, provide the app/engine versions and a description of the problem where available. Review screenshots and error messages for confidential filenames or paths before sharing them. Do not send sensitive documents or profiles unless an approved support arrangement permits it.
Privacy and current limitations
Processing is delegated to the installed engine on your computer. The desktop does not require an account for the workflow described here and has no telemetry integration. Optional Local AI communication is described in Settings. Also consider your own storage: a cloud-synchronized Documents folder, network share, backup tool, or external viewer may copy or transmit files independently of this app.
The app saves local job history, including input, profile, and output paths, and stores profiles containing original identity values in readable JSON. Do not assume these are encrypted or erased when you clear the queue or delete history. Use appropriate device access controls and storage policies.
Current interface limits to keep in mind:
- Inspect is a sample display, including its BEFORE / DIFF / AFTER controls, findings, and Export audit log / Open buttons. It is not connected to completed jobs.
- Verify shows a fixed example. Replace, Re-run with these tokens, Open in inspector, and Export verify log do not perform those actions.
- AUTO-VERIFY AFTER JOB: On in Settings is a static label, not evidence that a check ran. Check for updates is not wired to an updater.
- There is no visual editor for arbitrary find/replace pairs or scrub rules in the current Profiles screen. Scrubbing is not available in this workflow.
This manual does not promise complete detection, removal of every kind of hidden content, reversibility, or compliance with a particular privacy standard. Treat every output as needing review under your own sharing and retention requirements.