Get help without losing work
Preserve your draft and existing operation before trying recovery. The goal is to recover the original task, not to erase its state or submit duplicate work.
Preserve the failing state
Keep unsent text, saved file locations and any request or run identity. Record the visible error before dismissing it. Do not clear a draft, reset permissions or recreate work merely to reproduce the issue.
Find the matching checks
Keep your original attempt here while choosing the checks to read. Use non-sensitive text; this helper keeps it only in this page and does not send or execute it.
All checks are available. Nothing is sent or executed.
403 / Forbidden
Record the service, time and non-secret error code. Confirm the intended account and workspace. Do not disable origin checks or share authorization headers.
401 / Sign in required
Keep your draft before signing in. Website sign-in and native device approval are separate steps. Return to the original task and check its state before sending a write again.
202 / 409 / Work is still pending
Keep the original request or run identity. An uncertain outcome is not permission to submit duplicate work or create a fresh request key. Inspect the original operation before retrying.
The wrong mode opened
Check the first character and the active mode before pressing Return. An explicitly selected mode takes precedence over leading-symbol routing.
Voice input does not respond
Finish active dictation or recording, identify the voice feature that failed and read its status. Check only the relevant Microphone or Speech Recognition permission. Do not grant unrelated access.
Music repeatedly asks for a Keychain password
Cancel unexpected repeated prompts. Keep the app version and requesting process name for support. Never delete Keychain items or weaken their access rules.
Record useful details
Fill in this report with non-sensitive details. Include the installed app version for native issues, or the page URL for website issues; a website update does not identify the binary installed on your Mac.
# Support report
- Product and installed version:
- Exact action:
- Expected result:
- Observed result and non-secret error:
- Relevant operation/run ID, if safe to share:
- Steps already tried:
- Work preserved before retrying:
Keep exact error text or status where safe, rather than only saying that it failed. Remove cookies, API tokens, provider keys, device approval codes and private inputs. Review screenshots for account details and document text before sharing them. Use a minimal reproduction with non-sensitive material where possible.
Choose the matching recovery guide
- Ouros X: shortcut or note save
- Zilch: extraction failure
- Loop Builder: uncertain build or run
- Shared account and access
For an asynchronous request, acceptance is not completion. MDN's explanation of HTTP 202 describes that HTTP distinction; inspect the owning product's operation record for the actual outcome.
Check the correction
Return to the original task's success check. Reveal and read the saved note, inspect the existing extraction and its warnings, or inspect the same loop run. A successful sign-in or reset alone does not establish that your work completed.
If the symptom remains, stop repeating the action and retain the current state. Contact Ouros with the sanitized report and the checks already tried. See website changes and Mac version guidance when confirming which release is relevant.