Reproduce the problem with fictional words first. A support report usually needs the conditions that caused the failure, not the client's sentence that happened to be on screen. This matters for wrong-field pastes, unexpected rewrites, model downloads, and provider errors. SuprFlow 1.0.0 also prints transcript excerpts on some diagnostic paths, so a raw log or screenshot should not be sent without inspection.
Capture the smallest useful report
| Include | Example that avoids real client material |
|---|---|
| App and Mac | Signed SuprFlow version, macOS version, Mac chip, and whether the device is managed. |
| Recognition setup | Speech model, language, actual microphone, and whether the recording was short or long. |
| Writing path | Formatting provider category (Default, Cloud API, or Local (Ollama)), model, and destination app/field type. Share a custom endpoint's host only if your policy permits; never include an API key or token. |
| Steps | “Focus a blank Notes field; press Fn; say the synthetic sentence; release; switch windows only in test 2.” |
| Expected and actual | “Expected ‘Project Elm did not approve 17 units’; got ‘Project Elm approved 70 units’ in the test field.” |
| Frequency | Number of repetitions, whether it happens after relaunch, and what changed when one variable was altered. |
Use a fresh fictional sentence for each test if an error may be cached in history, clipboard, or a cloud provider account. When diagnosing a wrong-window paste, use two empty test notes clearly labeled A and B. When diagnosing a formatter failure, use a test provider account and a harmless text paragraph. When diagnosing a model download, record the displayed state and percentage; there is no reason to attach dictated text.
Inspect attachments before sending
- Crop screenshots to the SuprFlow control and the fictional result. Check the browser address bar, tab names, window title, notifications, and nearby document text.
- Search any log or diagnostic bundle for client names, amounts, account or matter identifiers, transcribed phrases, API keys, URLs with tokens, file paths, and personal email addresses. SuprFlow 1.0.0 prints recognized-word excerpts in streaming, batch, tail, and chunk paths, so treat console logs as potentially containing dictated words.
- If support requests a recording, ask whether a synthetic recording reproduces the issue. Do not send a real client call or meeting merely because the app was involved.
- If a confidential note pasted into an unapproved destination, follow your organization's incident procedure before treating it as an ordinary support ticket. Preserve the facts needed for containment without spreading the text again.
Do not infer from a privacy policy that diagnostics are automatically safe to forward. Obtain the current support address from the vendor's live site or purchase correspondence at the time of reporting.
Questions people ask
Does SuprFlow need the real sentence to debug recognition?
Often a fictional sentence with the same shape is enough: similar name sounds, an acronym, a negation, and a number. If the issue only occurs on real content, ask for a secure, approved escalation process rather than pasting that content into an ordinary ticket.
Can I share a Console export as-is?
Do not assume so. Apple's Console app allows log messages to be viewed and shared; SuprFlow 1.0.0 includes transcript excerpts in some diagnostic prints. Search and redact under your firm's policy before sharing any archive.
What if the bug involves a cloud provider error?
Give the provider category, model, timing, HTTP status if shown, and a synthetic reproduction. Do not send the API key, full request body, or provider error text until it has been checked for echoed transcript data.
Related guides
- Can dictation appear in Mac diagnostic logs?
- Fix text that did not paste
- Investigate invented words after silence
- Recover when AI formatting fails
- Report a wrong-destination paste