Sync maintenance
Open Settings → Sync Settings → Maintenance for database-level repair and cleanup. These actions are not part of routine pairing or day-to-day synchronization. Before using them, let active writes finish and keep a current backup of data you cannot recreate.
Choose the narrowest repair
- Delete Sync Database removes the local sync database. This is destructive local recovery, not a normal way to disconnect a device.
- Sync measurables, dashboards, habits, categories, AI settings sends that shared configuration again. A dialog lets you choose which kinds to include — labels and saved task filters are offered too — before you choose Start sync.
- Message history queues entries again for your other devices. Choose a range — All, Last 30 days, or Custom with a start and end — and the entity types to include, then Start. If some entries fail, Retry failed entries repeats just those.
- Populate sync sequence log indexes existing entries so that backfill can answer requests for entries created before sequence tracking existed.
- Purge old sent outbox items deletes sent outbox rows older than 7 days and reclaims disk space. Items that are still waiting or failed are kept.
Start with the smallest operation that matches the symptom. A stuck attachment belongs in the Outbox; persistent sequence gaps belong in Backfill sync; two valid concurrent edits belong in Conflicts. Deleting the sync database should be a last-resort local reset performed with a known-good peer and backup available.
After a repair, return to Matrix Stats, confirm that applied work is advancing and the queue drains, and check that the Sync Outbox and the Backfill missing count settle.