Fix a notification preference that will not save

Recover from “Couldn’t save” by retrying one notification setting, verifying the signed-in session, and confirming the value after a fresh server read.

Last reviewed

A notification preference is saved only after the authenticated PUT succeeds. The exact mobile fallback error is Couldn’t save. Try again.; the web toast title is Couldn’t save.

Notification save-error workflow checking initial load, authenticated partial update, rollback, fresh read, and push registration.
The server-confirmed setting is the value that remains after reopening the page. Open full-size screenshot.

Steps

  1. Confirm the signed-in account and reopen notification settings. If the page says Couldn’t load notification settings., select Retry before attempting edits.
  2. Change one switch. Do not use an API key: /api/me/notifications requires a session because it changes account behavior rather than file access.
  3. If the value rolls back, restore connectivity and verify the session has not expired. Then retry that same switch once.
  4. Leave and reopen the screen. GET returns the effective server state for all 14 groups, nested opt-ins, and three channels.
  5. For a Push failure, separately verify OS permission and physical-device support. A native registration error can occur after the account channel was already saved.
Dosya profile notification settings used to verify a server-confirmed preference after retry.
Reopen the signed-in account setting after resolving the failed save. Open full-size screenshot.

The endpoint ignores unknown keys. It batches valid preference/channel rows and records a profile update audit event. Missing stored rows use documented defaults; therefore a reloaded value may be a default rather than a database row, but it is still the behavior delivery uses.

Expected result

The edited switch survives a fresh settings load and controls later eligible notifications. No file, share, workspace role, or existing inbox row changes during the preference write.

Troubleshooting

The screen never leaves its load error. Reauthenticate or check API connectivity, then press Retry. Editing is unavailable until the server list arrives.

The message contains a specific server error. Resolve that condition first; mobile displays an Error.message instead of replacing it with the generic fallback.

Only Push still fails. A saved account setting is insufficient without a platform token. Repair OS permission and toggle Push again on a physical, configured build.

Was this helpful?

Loading helpfulness results…

Voting saves a necessary ballot cookie for up to 180 days so you can change your answer.

Questions and replies

Ask about the steps in this guide. Questions are reviewed before publication.

Keep account details, credentials and private files out of public questions. Use private support for those.

Loading questions…

    Sign in to your Dosya account to ask a question.

    Check the outcome before you retry

    Use these shared checks when a task needs a second look.