Convo uses a multi-layered sync system to keep your conversations safe and accessible. This guide helps resolve issues with conversations not syncing, data recovery, and cloud storage.
How Convo sync works
Convo uses multiple storage layers for reliability:
- • Real-time: Active conversation in memory
- • Local storage: Automatic crash recovery backup
- • ChromaDB: Vector database for AI context
- • Cloud backend: Permanent PostgreSQL storage
Common issues
Conversations not appearing in dashboard
If recorded conversations don't show in your dashboard, sync may have failed.
Common causes:
- Not logged into account
- No internet during or after recording
- Session expired (JWT token invalid after ~30 days)
- Backend server temporarily unavailable
Solutions:
- Verify you're logged in (check account name in app)
- Ensure active internet connection
- If session expired, sign out and sign back in
- Restart Convo to trigger automatic retry
- Wait a few minutes (sync can be delayed)
Note: Conversations sync to cloud at the end of each recording session. If you're still recording, it won't appear in dashboard until you stop.
Crash recovery not working
Convo saves conversations locally every 10 segments to prevent data loss. On next launch, unsaved conversations are automatically recovered and uploaded.
How recovery works:
- During recording, segments saved locally every 10 segments
- On next launch, Convo detects unsaved conversations
- Recovered conversation uploaded to dashboard
- Notification: "Recovered conversation from previous session"
If recovery fails:
- Restart Convo (recovery happens automatically)
- Wait 30-60 seconds for process to complete
- Check internet connection (recovery requires upload)
- Data retained and retries on next launch if failed
- Very short recordings (under 30 seconds) may not trigger recovery
Session expired error
Authentication tokens expire after ~30 days for security, or when you change your password.
- Click "Sign Out" in Convo
- Sign back in with email and password
- Previous conversations re-sync from cloud automatically
- Locally recorded conversations upload once authenticated
Offline recording not syncing
Convo can record offline, but syncing to cloud requires internet. Offline recordings save locally and sync automatically when connectivity restores.
Works offline
Audio recording, transcription, local crash recovery
Requires internet
Cloud sync, AI suggestions, coaching features
Solutions:
- Connect to internet after offline recording
- Keep Convo running 2-3 minutes for sync
- Check dashboard to verify conversation appears
- Restart Convo if it doesn't appear
- Offline queue holds 50 messages; older messages dropped if full
ChromaDB storage errors
ChromaDB is a local vector database for AI context. If it fails, Convo falls back to in-memory storage—your conversations are still safe.
- Restart Convo to trigger automatic ChromaDB recovery
- Conversations stored in cloud backend (safe)
- AI suggestions may be limited until restored
- Check Console.app for ChromaDB errors (search "ChromaDB")
Data safety: Even if ChromaDB fails, conversation data is safe. Convo automatically falls back to in-memory storage and syncs to cloud backend when recording ends.
Verifying sync status
Check authentication
- • Look for account name/email in Convo toolbar
- • If you see "Sign In", you're not authenticated
- • Sign in to enable cloud sync and backup
Check connectivity
- • Verify you can access other websites
- • Check if firewall is blocking Convo
- • Try disconnecting VPN temporarily
- • Recommended: 10+ Mbps for reliable sync
Check backend health
Convo checks backend health on launch. If backend is down for maintenance, sync temporarily unavailable but resumes automatically when restored.
Advanced troubleshooting
Check sync logs
Console.app provides detailed sync info:
- • Filter by "ConvoPal"
- •
[WebAPI] - Backend sync status - •
[ChromaDB] - Local database ops - •
[CrashRecovery] - Recovery attempts - •
[WebSocket] - Connection status
Sync timeouts and retries
- • Standard API requests: 15 seconds
- • Batch segment upload: 30 seconds
- • Retry attempts: 3 with exponential backoff (1s, 2s, 4s)
- • After max retries: Saved locally, retry on next launch
Best practices
Prevention
- • Stay logged in for automatic sync
- • Use stable internet during and after recordings
- • Let recordings finish and sync before quitting
- • Wait 2-3 minutes after recording for sync
- • Restart Convo daily to clear caches
What's safe to do
- • Quit after recording ends (sync automatic)
- • Record offline (syncs when online)
- • Use on multiple devices (conversations sync)
- • Uninstall/reinstall (conversations in cloud)
When to contact support
Contact support if you experience:
- Conversations not syncing after 24 hours
- Crash recovery failing repeatedly
- Duplicate conversations in dashboard
- Auth errors persisting after re-login
- Lost conversation data not recovered
Include when contacting support:
- • Account email address
- • Date/time of affected recording
- • Whether online or offline during recording
- • Any error messages
- • Console.app logs (filter "ConvoPal")
Contact: ivan@itsconvo.com
Related articles