Find the failing stage
Empty or delayed transcript
- Confirm the intended microphone and system audio sources in Settings → Audio & meetings. Test both sides of a short call.
- Check the selected transcription engine. If it uses a cloud account or API key, verify that provider’s access separately from chat-model access.
- Run Run diagnostics in the transcription controls. Save the specific failing step and redacted error.
- For batch transcription, allow the current batch to finish. Where available, Max batch duration (seconds) controls batching; a shorter batch can reduce delay but will not recreate audio that was never captured.
- For an active meeting, configure Live meeting notes and verify a new test sentence. This does not backfill a past call.
Transcript exists but summary fails
- Preserve the meeting note and transcript. Copy any important manually written notes before retrying a summary that may update the note.
- Check the provider selected for that summary. Screenpipe allowance, ChatGPT sign-in, an Anthropic API key, and Ollama are different access paths. See AI access requirements.
- Test one small question against recent recordings. For a custom provider, use its AI preset’s Run diagnostics. A successful text response still needs a successful recording-tool call.
- Follow the error’s recovery action: sign in for authentication errors, wait for the specified rate-limit interval, or correct the endpoint/model. Avoid repeatedly launching duplicate runs.
- Retry the meeting summary once the failing step works. Confirm the result is saved to the intended meeting and matches its transcript and time range.
Error: invalid bundled pi compaction patch
This message concerns Screenpipe’s bundled AI runtime patch. It is not the name of a transcription setting, and toggling live captions will not repair it. Record your app version, OS, exact error, and whether the failure happens in chat, a meeting summary, or a scheduled task. Check for an available app update through the normal update flow, quit Screenpipe fully once, reopen it, and retry a small task. Do not delete~/.screenpipe, erase recordings, or replace a globally installed Pi package as a workaround for a bundled-runtime error.
If it persists, contact support with the details below. A source-code fix or newer version number alone is not proof that your installed build contains a fix; report the version you actually tested.
What to include when asking for help
- Screenpipe version and OS version
- Meeting date, approximate time, and timezone
- Whether audio, transcript, and summary each exist
- Transcription engine, live-caption provider, and summary model
- Exact error and the diagnostic step that failed
- A short reproduction and what happened after one retry