What a health-notice ticket usually is. Almost all of them are one of three things: the member expected a limit and got a dialog, they expected the dialog once and got it again, or they withdrew one and expected their plan to change back. None of them is a fault.
What the notices are
Two settings show a short health notice before Loopa applies them:
- A protein target above 1.2 g per pound (2.65 g/kg) of goal weight
- A fast planned for 48 hours or longer
Neither is a limit. There is no maximum protein target, and a fast may be set up to 40 days. The notice exists so nobody arrives at one of those without having been told what it involves. The member reads it, taps the accept button, and Loopa saves exactly what they asked for.
The three common tickets
"It won't let me set my protein target"
It will. Ask what they saw after they tapped the accept button on the notice. Almost always the save went through and they had not looked. If they tapped the other button, the target was not saved, which is correct.
If they say the number came back different from what they typed: that was the OLD behavior, before 2026-08-26. Targets above 1.5 g/lb used to be silently reduced to 1.5. They are not any more. Ask them to set it again.
"It keeps asking me"
Expected. An acknowledgment covers the one setting or the one fast it was given for. A different protein figure, or another long fast, asks again. There is deliberately no "do not ask me again": a blanket switch turns the notice into something ticked once in a different frame of mind.
It should NOT ask when nothing changed. Re-saving a target they already acknowledged does not raise the notice. Only changing the value does. If a member reports being asked while saving something unrelated (their water goal, say) and their protein figure was untouched, that is a defect worth escalating with the exact steps.
"I withdrew one and nothing happened"
Also expected, and the wording says so. Withdrawing changes the future, not the past. Their targets keep their values and a fast in progress keeps running; what changes is that the next high-protein save or long fast shows the notice again.
Withdrawing does not erase the entry either. It stays in the list, marked as withdrawn, because a withdrawn acknowledgment is still the record that one was given. Deleting the account deletes both.
Where the member sees their record
You → Preferences → Your Data → Health notices you accepted in the app. The list is served to the apps, so that is where a member reads it.
Each entry shows the notice, when it was accepted, and from which device, plus a status:
| Status | Means |
|---|---|
| ACTIVE | Accepted and not yet spent, so it will permit the next matching save |
| USED | It permitted the save or fast it was recorded for. Normal; this is what most entries look like |
| SUPERSEDED | The notice's wording changed after they accepted it, so they will be asked again |
| WITHDRAWN | They withdrew it |
What extended fasts do
Presets now run 16:8, 18:6, 20:4, OMAD, 24 hours, 48 hours, "3 days · 72h" and 7 days, plus a custom duration up to 40 days. Below three days a custom target is set in hours; at and above it, in whole days.
While a fast of 48 hours or more is running the member sees a hydration and electrolyte strip on the fasting screen, which is deliberately not dismissable, and, only if they already have notifications on, one reminder a day. Loopa never asks for notification permission because somebody started a fast, so "I did not get the daily reminder" usually means notifications are off for Loopa. Check that before anything else.
Ending a fast is always one tap. If a member reports otherwise, escalate. That is a defect, not a policy.
What to escalate
- A member says the notice appeared and their save was refused after they accepted it, twice in a row.
- A member says a target or a fast duration was changed to a number they did not choose.
- A member says the fasting timer shows an obviously wrong duration on a multi-day fast (check whether a daylight-saving change falls inside it and say so in the ticket).
- Anything where a member reports they were not shown a notice before a high-protein target or a 48-hour-plus fast was applied.
Include the exact figure they set, which surface they used (phone app, or a browser), and the date and time. The tenant nginx access log and their acknowledgment record together answer most of these in minutes.
What NOT to tell a member
Support does not give clinical guidance. If a member asks whether a protein target or a fast length is safe for them, the answer is that Loopa is a general wellness product, the notice cites a published source, and the question is one for their clinician. Do not estimate, reassure, or talk them out of it.
