Note saving problems

A note saves on your device and synchronises separately. Read the exact message before choosing a recovery action: a local save failure is different from a conflict with a newer version.

If the latest text did not save locally

If Oudden says it could not save the latest changes on this device, the text may still be visible in the editor but must not be treated as safely saved.

Keep the note open while you preserve the text you need.
Select and copy the important text into another document or trusted local editor.
Check that the copy contains your latest changes.
Follow any recovery action shown by Oudden. If the error remains, contact support.

Do not start by resetting app data, signing out or deleting the note. Those actions are not a substitute for preserving the unsaved text.

If synchronisation needs attention

A connection problem can delay the server copy even when your local text is saved. Check the connection and the status shown for the note. If Oudden asks you to review an older offline change, use Refresh and retry when offered and read the resulting state before choosing another action.

Do not assume that Retry means the server accepted the change. Wait for the operation to finish. Until the current content reaches the server, another device or a recipient may see an older version.

If there is a newer version

Oudden may show This note changed elsewhere or ask which version to keep. If your current note has edits, there may be two useful versions.

Save mine as a copy preserves your edits in a separate note. Use it when you need to keep the local work before comparing versions.
Use latest version accepts the newer server version. Choose it only when you no longer need the local changes or have preserved them elsewhere.

Not every warning offers the same buttons. Read the description beside the actual actions. Do not interpret accepting the latest version as merging both texts automatically.

If the server rejected a change

The warning explains that the local text is still available and offers the applicable recovery actions. Depending on the situation, these may include creating a copy or keeping the server version. Preserve important local text before choosing an action that discards it.

A recovery copy is not proof that synchronisation has completed. Check its status before relying on it on another device or sharing it.

A content warning prevents saving

If the message identifies an invalid link, unsupported content or a note that is too large, follow its explanation. Preserve a copy of the text first, then correct the link, simplify the affected block or shorten the content as requested. A connection retry alone does not fix a content validation error.

If you cannot identify the affected area, keep the note open and contact support with the exact message. Do not delete the whole note to remove the warning.

If an AI edit or sharing is blocked

Chat and sharing may need a saved, current note before continuing. Resolve the saving or version warning first, then retry the intended action. An outdated AI proposal should be requested again against the current note; it should not overwrite newer manual edits.

Changing the local voice-input history or audio-retention settings does not repair note synchronisation. Those settings control different data.

Get help without sending the whole note

If recovery still fails, contact support with:

your operating system and Oudden version;
the exact warning and error code, if shown;
the action that triggered it and whether you were offline;
whether you managed to preserve a copy of the latest text.

You do not need to send meeting content, passwords or private note links to explain the problem. Keep your preserved copy until the issue is resolved.