When something doesn't go to plan, start here. Each problem below has one fix that resolves it most of the time.
A recording won't finish uploading
A recording streams to the cloud as it's captured, and a local copy is kept until the server confirms receipt — so the audio is safe even when the upload stalls. A stalled upload resumes on its own once the connection is healthy.
Fix: confirm you're online, then reopen the app or web recorder. The held chunks finish uploading from where they left off. Don't delete the recording — that's the one thing that can lose the audio that hasn't confirmed yet.
Can't sign in
Sign-in fails most often because of a stale session, not a wrong password.
Fix: sign out fully, then sign back in with the same account you use on the web. If a CLI command reports an auth error, refresh your token:
Cast handoff failed
A cast can fail to connect when the phone and the TV aren't on the same network, or the target is an audio-only device.
Fix: put both devices on the same Wi-Fi and pick a video-capable TV — Apple TV, Chromecast, or a Roku. HomePods and other audio-only AirPlay devices can't render the stream and are hidden as targets. See cast to a TV.
Notes or context aren't generating
Transcription and extraction run after a recording completes. If nothing appears, the recording usually hasn't finished uploading, or it captured no speech.
Fix: check the recording reached uploaded in your team's Media section. A silent recording produces no transcript and therefore no summary or decisions — narration is what the pipeline reads.
Never delete a recording to "reset" a stuck upload. The local copy is your safety net until the server confirms receipt — deleting it can lose audio that hasn't uploaded.
What's next
- Get the most out of SageOx — the habits that keep things smooth.
- Context capture overview — how recordings become context.
- ox doctor — diagnose CLI and connection issues.