Skip to main content
  1. Find the saved copy. If editing in the app, confirm Save completed. If editing a local file, confirm it is a valid UTF-8 .md file within the actual mounted vault returned by nlkb orient.
  2. Inspect health. Run nlkb doctor and nlkb status. Check the connection card, network, background service, and whether synchronization is paused. Installing the desktop viewer alone does not pair a machine.
  3. Check the direction. For local-to-cloud, confirm write permission and that the local operation is accepted. For cloud-to-local, compare the saved cloud page with the mounted file. Do not use an old export as the replica.
  4. Inspect conflicts. Competing edits can preserve a candidate while the normal local path contains accepted cloud text. Review Conflicts before assuming the candidate was lost.
  5. Follow the reported health issue. A missing root needs investigation; paused synchronization still queues local changes. Use sync health for service and root checks. Do not delete managed state or reset enrollment to try to clear an unexplained error.
Resolved when: a harmless agreed edit appears in the other copy and health no longer reports the blocking problem. If not, contact support with the direction, time, platform/version, and redacted health output. Preserve the affected files.