Connection & Recovery Issues

This means the live connection to Kalima's transcription engine dropped, usually a brief network blip or a server hiccup. Keep recording. Your audio continues to be saved locally and Kalima automatically retries to reconnect, resuming the instant your device reports it is back online. Anything missed while you were disconnected is re-transcribed afterward and merged into the transcript in the correct place. There is nothing you need to do but wait.

A longer outage couldn't be recovered automatically, so Kalima paused and is checking in with you. Choose Resume recording to continue the same session once your connection is back, or Stop session to finalize what you have. If you resume, recording carries on and the missed stretch is still re-transcribed and filled in. If you stop, the audio you captured is finalized and any recoverable gap is transcribed afterward.

This is expected. When a stretch is re-transcribed by gap recovery (rather than transcribed live), it arrives a little after the live portion and is marked as recovered so you know it was filled in after the fact. It is merged into the right spot on the timeline, with the same languages, translation, and session context as the rest of the recording. No action needed, it is the system doing exactly what it should.

Occasionally a missed stretch can't be recovered on the first try. When that happens, Kalima offers a retry option, use it to attempt recovery again. Recovery needs the locally recorded audio for that window to still exist, so retry from the same device and session where you recorded. Note that very early audio captured in the first moments before the first words can occasionally be hard to recover.

Keep recording. Kalima is built to ride through a flaky connection: it buffers recent audio during a drop and sends it once reconnected, so the conversation continues without restarting the session. Stopping and starting over is rarely necessary and only creates extra takes. If the latency badge is yellow or red, that's a sign of a slow or unstable network, but your recording is still safe.

If you know in advance the location has poor signal, see the offline approach below.

Yes. With no connection, Kalima switches to offline recording: an Offline, recording locally indicator appears, live text is paused on purpose (to avoid stale partial results), and your audio is saved on your device. When you reconnect, or when you stop, the entire offline stretch is transcribed automatically using your session's original settings and added to the transcript. This is ideal for recording on a plane, in a basement, or anywhere with no signal.

Almost certainly not. Kalima saves your audio continuously in small pieces (roughly every few seconds) as you record, specifically so an unexpected crash doesn't lose your work. Reopen Kalima and return to the session to recover the captured audio. The local recording stays on your device for playback and recovery and is not affected by the crash.

The latency badge reflects how fast transcription results arrive over your current connection. Yellow or red usually means a slow or unstable network, or a high-latency input device. Try moving closer to your router or switching to a stronger or wired network. Bluetooth/wireless headsets and virtual audio cables also add delay, if Kalima shows a device latency advisory, switching to a wired or built-in microphone helps. See Microphone & Audio Issues for more.

You're billed for transcription against your balance, and recording stops automatically when your balance runs out (after a low-balance warning and a short grace countdown). Recovered stretches are transcribed with the same languages and translation as your live session. If recording stopped on its own, it was because your balance hit zero, not the connection, see Billing & Balance Issues.

After reconnecting, give recovery a moment to finish, recovered text arrives after the live portion, not instantly, and is marked once merged. Read through the recovered section once it lands; Kalima also shows fainter words where the engine is less confident, which is a useful cue for any spots worth a quick check. For tidying anything that came through wrong, see AutoCorrect+.