When a Frewli water entry will not save

1. Read the message under the water button

On Today, selecting 250, 400 or 500 mL chooses an amount; the Add [amount] ml button logs it. The app can update the displayed total before the local write finishes. Watch the feedback beneath that button.

The short prompt uses the app’s latest overall saving state. It is not a separate saved receipt for every drink, nor an account-sync or backup status.

2. Retry the existing change

1. Leave Frewli open when the warning appears.
2. Read the detailed error shown below the warning.
3. Choose Retry saving.
4. Allow saving to finish and check whether the warning returns.

The retry writes the app’s current local record again. It does not add another water entry. That current record can include other changes you made after the original problem, so the action is broader than resending one isolated sip.

A failed write can leave the new water visible in the running app. Keep the installation and current session available while resolving it; do not assume the visible change is safely stored just because you can still see it.

3. Check the difference with one example

Imagine Today shows 1,000 mL before you record a 250 mL drink. The visible total becomes 1,250 mL, then the save warning appears.

Retry saving tries to store that current record, still containing one new 250 mL entry. Pressing Add 250 ml again creates a second entry; the visible total would become 1,500 mL, assuming no other changes. The extra tap is another drink record, even when the first write had not succeeded.

These numbers illustrate record keeping, not an amount you should drink. For choosing a portion from a bottle label, use the separate bottle-volume guide.

4. Treat the short Undo window separately

The latest quick-water confirmation includes Undo for about five seconds. That window ends independently of the save result. A disappeared prompt is not evidence that saving succeeded, and a slow write does not become a failed write simply because five seconds passed.

If the latest quick entry was accidental and Undo is still available, it removes that entry locally and starts another save. Read any warning from that save too. Undo is not a general history editor or a way to restore all older records. If you accidentally added twice and the short control is gone, explain that to support before trying a broader reset.

5. Separate local saving from Apple Health

A missing Apple Health copy and a Frewli local-save warning are different problems. The local confirmation does not establish that Health received a sample. Health access, export and imported copies have their own rules; follow the Health water guide when that is the missing piece.

Undo can cancel a pending local Health export, but it does not remove a sample already exported to Health. Adding another Frewli drink to make a Health total change can create an extra local entry.

6. Keep the record while asking for help

If the warning remains after retrying, contact Frewli support with the app version, exact error wording and which action preceded it. Leave private health history, sign-in codes and unrelated personal details out of screenshots.

The warning alone does not identify one universal cause. Do not diagnose it as a network, Health-permission or storage-capacity problem from the red message alone. Frewli 1.1.6 works offline without backend sync, as its App Store release information explains. There is no account refresh that confirms this write.

Keep your existing installation while seeking help. Reinstalling or erasing device data is not a retry: erasure covers the whole local record, with no in-app Undo. Read what the offline update means for stored history before considering a wider data action.