Session Interruption Crash Recovery

The recording app received SIGKILL at t=19:54 into a 20-minute encounter. The ring buffer held 280ms of audio that had not entered the write path. On relaunch the recovery pipeline reports recovered_duration_ms=1194000 and last_f…

Agent generates the draft note from recovered audio but sets status to DRAFT and surfaces a specific, named truncation warning in the clinician review screen: 'Recording ends at 19:54; up to 280ms immediately before the crash may be unrecovered. Review the note for completeness before signing.' Age…

A force-close was triggered after 14 audio chunk write-completion callbacks fired successfully at the app layer. fsync() was never called. The OS page cache was not committed to NAND. On recovery all 14 chunk files on disk are ze…

Agent reads chunk_file_sizes_bytes and detects all values are zero, regardless of chunk_write_callbacks_succeeded=14. Agent raises RECOVERY_FAILED, does not issue any upload call to the transcription pipeline, and surfaces a clear message to the clinician: 'Audio data from this session could not be…

The app crashed mid-write of the final AAC frame in chunk-9, the last chunk of a 9-chunk session. Chunk-9 has valid decodable frames for bytes 0–87,234 and a partial, undecodable frame occupying bytes 87,235–89,011. Chunks 1–8 ar…

Agent truncates chunk-9 at byte 87,234 (the last valid frame boundary), discards bytes 87,235–89,011, and submits only the truncated chunk-9 to ASR. Agent computes effective recovered duration from valid bytes across all chunks and displays this to the clinician. Agent surfaces a specific truncatio…