tmux-resurrect's autosave can fail silently, and unthrottled boot restore can OOM a Pi
tmux-resurrect + continuum bit me twice, both in ways that only show up after it's too late to do anything about it:
Autosave can fail silently. No error or logs, you just find out on the next restore that the file's empty or half-written.
Boot restore has no throttling. Continuum relaunches every saved session back-to-back with no delay. On a resource-constrained box (mine's a Pi) with 10+ heavy panes, that's enough to OOM it or hang SSH mid-restore.
What's worked for me: guarded saves every 5 min that get rejected if they're empty/half-written, plus a boot restore that brings sessions back one at a time with a delay between each. Runs as a systemd service, no login needed, survives reboot.
https://github.com/nahidspace/tmux-alwayson
If you've hit either of these, curious how you worked around it.