Session data recovery
Symptoms
Section titled “Symptoms”A session is missing expected transcript, summary, playback, or audio-copy behavior after a failure or application restart.
Likely causes
Section titled “Likely causes”Sessions persist database metadata, transcripts, summaries, status, and errors, but normalized-audio path persistence and audio-copy semantics are incomplete. Chat history is frontend-only and does not survive a reload.
Fast checks
Section titled “Fast checks”Check whether the session is still listed, inspect its status and error, locate the original source recording, and determine whether the missing item is transcript, summary, chat history, playback, or an export.
Resolution
Section titled “Resolution”Use the original source recording and existing session content to restart only the necessary workflow. For unavailable playback or audio copy after reload, do not assume a durable original-audio export contract; preserve the user-owned original separately.
Data-loss warning
Section titled “Data-loss warning”Do not edit synthezia.db or delete audio directories as a normal recovery action. Session deletion and reset cannot be undone through Synthezia.
Information to collect for support
Section titled “Information to collect for support”Collect session ID if visible, status, error, import versus recording origin, whether the issue occurs before or after reload, application version, and which data category is missing.