Auto-Save and Periodic Sync
Overview
Yeedu notebooks now include automatic saving and periodic synchronization features, ensuring your work is never lost. Changes are saved automatically at configurable intervals.
Auto-Save Features
Automatic Saving
- Real-time Saving: Changes saved as you work
- Periodic Sync: Automatic synchronization at intervals
- Backup Recovery: Recover work from saved versions
- No Manual Save Needed: Focus on your work, not saving
Save Indicators
- Saving...: Currently saving changes
- ✓ All changes saved: All work saved successfully
- ⚠️ Unsaved changes: Recent changes not yet saved
Configuring Auto-Save
Enable Auto-Save
- Open Notebook Settings (gear icon)
- Find Auto-Save section
- Toggle Enable Auto-Save on
- Choose save interval:
- Fast: Every 30 seconds (default)
- Standard: Every 60 seconds
- Slow: Every 120 seconds
- Manual: Save only when requested
Adjust Save Interval
- In Notebook Settings
- Set custom interval in seconds
- Shorter interval = more frequent saves (uses more resources)
- Longer interval = less frequent saves (more data loss risk)
Save Location
- Notebook cells automatically saved to database
- Cell content persisted
- Execution state not saved (re-run after restart)
- Versions kept for recovery
Markdown Cell Auto-Save
Markdown cells are also auto-saved:
- Edit markdown content
- Changes saved automatically
- Rich text formatting preserved
- Links and images retained
Periodic Synchronization
What Gets Synced
- Cell content (code and markdown)
- Cell order and structure
- Cell execution status
- Notebook-level metadata
- Custom parameters
Sync Behavior
- Local Changes: Made in real-time in your browser
- Queue: Changes queued for synchronization
- Periodic Sync: Pushed to server at intervals
- Confirmation: Sync status shown in UI
Handling Conflicts
If the same cell is edited in another session:
- Last saved version wins
- Notification of conflict appears
- Option to reload and merge manually
Working Without Internet
Offline Mode
If connection drops:
- Changes buffered locally
- Continue editing normally
- Connection restored automatically
- Pending changes synced immediately
Offline Indicators
- No Connection: Red indicator
- Syncing...: Yellow indicator
- Synced: Green indicator
Manual Save Operations
Force Save Now
- Click Save button (if visible)
- Or use keyboard shortcut: Ctrl+S (Windows) / Cmd+S (Mac)
- Immediate save to server
Save with Message
- Click Save with dropdown
- Add save note/message
- Helps track versions
- Useful before major changes
Version and Recovery
Version History
- Click Notebook menu
- Select Version History
- View all saved versions:
- Timestamp
- Last edited by
- Save message (if any)
Restore Previous Version
- Open Version History
- Click on previous version
- Preview changes
- Click Restore if satisfied
- Current notebook reverted
Compare Versions
- Select two versions in history
- Click Compare
- See side-by-side diff
- Review changes before restoring
Auto-Save and Performance
Impact on Notebook
- Minimal: Auto-save runs in background
- Large Notebooks: Longer sync times (notebooks > 10MB)
- Network: Slower internet = slower auto-save
- Frequency: More frequent = higher resource usage
Optimization Tips
- Use larger save interval for very large notebooks
- Reduce cell complexity to speed save
- Clear output before saving large files
- Archive old notebooks to improve performance
Troubleshooting Auto-Save
Changes Not Saving
- Check Save Status indicator
- Verify internet connection
- Check browser console for errors
- Try manual save (Ctrl+S)
- Reload notebook
Sync Failures
- Verify connection to Yeedu server
- Check network firewall rules
- Review browser console logs
- Try disabling browser extensions
- Clear browser cache
Lost Work Recovery
- Open Version History
- Find version before data loss
- Click Preview
- Verify content correct
- Click Restore
Best Practices
Optimal Settings
- Use Fast (30 sec) for critical work
- Use Standard (60 sec) for normal use
- Use Manual only for quick tests
- Always verify important changes are saved
Working in Teams
- Different users can edit different cells
- Be aware of conflicts
- Use descriptive save messages
- Review version history frequently
Data Loss Prevention
- Use version history regularly
- Save before major changes manually
- Take snapshots of important notebooks
- Archive notebooks regularly
See Also
- [Create Notebook](./Create notebook.md)
- [Editor Pane](./Editor Pane.md)
- [Notebook Types](./Notebook types.md)