SLUG: handling-low-fodmap-personalisation-tickets TITLE: Low FODMAP — settings, intake and the scanner TAGS: ["loopa","health","protocols","support"]
Low FODMAP: settings, intake and the scanner
Everything here is Premium on fodmap, except the digestive intake questions and the protocol picker, which are free.
"I set a group to 'no limit' and it still warns me"
Almost always correct, and the reason is the phase.
Tightening acts everywhere. Loosening acts in Personalisation only. Setting a group to leave it out takes effect immediately in any phase. Setting one to no limit does nothing until the member reaches Personalisation.
That is deliberate. Loosening during Restriction changes the trial the end-of-phase assessment is about to score, invisibly, so the result would be about a diet nobody recorded. Loosening during Reintroduction breaks the requirement that the background diet stay low, which is the only thing that makes a single challenge mean anything.
Check which phase they are in before treating this as a fault.
"My fructan setting isn't being applied to bread"
Check whether they set the parent or a family. Fructans split four ways: wheat and grains, onion and garlic, fruit, vegetables. A family with no setting of its own inherits the parent, and a family that has one overrides it.
So fructans: leave it out plus fructans (wheat and grains): no limit is a member who is avoiding onion and eating bread, and both halves are working.
"I marked a food as fine and it still says No data"
Working as designed, and worth explaining rather than escalating.
A personal mark that a food bothers them can refuse at any evidence level. A mark that it is fine can only clear a food Loopa has a complete published measurement for. It cannot turn an unmeasured food green.
The reason is that "I get on with this" is evidence about the member, not about what is in the food. If Loopa has never had a measurement for it, a personal mark does not create one. The mark is still shown on the item, beside the honest No data.
"Loopa says Low FODMAP isn't recommended for me"
A recommendation state, never a block. It appears when the member reported celiac disease, Crohn's or ulcerative colitis and did not report an IBS diagnosis.
The tile stays selectable, says "Not recommended based on your answers", and opens one acknowledgment screen with Start anyway. There is no second confirmation and nothing is hidden. If a member says they cannot select it, that is a real fault — get the screenshot.
Loopa records that they chose it against the recommendation, and their coach can see that. It changes nothing about how the protocol runs.
"I said I'd already finished elimination and it started me at the beginning"
Partly expected. Loopa starts them as far along as the phase rules allow, and some phases have requirements it cannot waive — Reintroduction needs a baseline to compare against, and a brand-new account has no logging behind it.
The app shows the refusal reason (baseline_too_short, transition_not_allowed) rather than silently resetting them. Their answer is stored either way, so nothing they told us is lost.
"The scanner said my cereal bar is red and it's a health food"
Read the flagged term back to them. The scanner reads the ingredient list, not the nutrition panel, and high-fibre bars are very often bulked with inulin or chicory root, which are fructans.
Two entries are deliberately soft: erythritol and natural flavors are flagged as worth noticing, not as a refusal.
An ingredient list Loopa recognises nothing in returns No data, not Compatible. That is not a failure to answer — it is the honest answer, because an ingredient list says what is present and never how much.
"The scan gave calories but no FODMAP reading"
Check three things in order: they hold Premium, they have a live protocol, and the product resolved with an ingredient list. Not every source publishes one. Without ingredients there is nothing to read, and Loopa does not guess.
What never happens
Nothing in Low FODMAP refuses to log food. Every check and every scan carries Log as planned anyway. A ticket that says Loopa would not let them record a meal is a real bug, not the protocol.
SLUG: handling-low-fodmap-personalisation-tickets TITLE: Low FODMAP — settings, intake and the scanner TAGS: ["loopa","health","protocols","support"] --- # Low FODMAP: settings, intake and the scanner Everything here is **Premium on `fodmap`**, except the digestive intake questions and the protocol picker, which are free. ## "I set a group to 'no limit' and it still warns me" Almost always correct, and the reason is the phase. **Tightening acts everywhere. Loosening acts in Personalisation only.** Setting a group to *leave it out* takes effect immediately in any phase. Setting one to *no limit* does nothing until the member reaches Personalisation. That is deliberate. Loosening during Restriction changes the trial the end-of-phase assessment is about to score, invisibly, so the result would be about a diet nobody recorded. Loosening during Reintroduction breaks the requirement that the background diet stay low, which is the only thing that makes a single challenge mean anything. Check which phase they are in before treating this as a fault. ## "My fructan setting isn't being applied to bread" Check whether they set the **parent** or a **family**. Fructans split four ways: wheat and grains, onion and garlic, fruit, vegetables. A family with no setting of its own inherits the parent, and a family that has one overrides it. So *fructans: leave it out* plus *fructans (wheat and grains): no limit* is a member who is avoiding onion and eating bread, and both halves are working. ## "I marked a food as fine and it still says No data" Working as designed, and worth explaining rather than escalating. A personal mark that a food **bothers** them can refuse at any evidence level. A mark that it is **fine** can only clear a food Loopa has a complete published measurement for. It cannot turn an unmeasured food green. The reason is that "I get on with this" is evidence about the member, not about what is in the food. If Loopa has never had a measurement for it, a personal mark does not create one. The mark is still shown on the item, beside the honest *No data*. ## "Loopa says Low FODMAP isn't recommended for me" A **recommendation state, never a block.** It appears when the member reported celiac disease, Crohn's or ulcerative colitis and did **not** report an IBS diagnosis. The tile stays selectable, says "Not recommended based on your answers", and opens one acknowledgment screen with **Start anyway**. There is no second confirmation and nothing is hidden. If a member says they cannot select it, that is a real fault — get the screenshot. Loopa records that they chose it against the recommendation, and their coach can see that. It changes nothing about how the protocol runs. ## "I said I'd already finished elimination and it started me at the beginning" Partly expected. Loopa starts them as far along as the phase rules allow, and some phases have requirements it cannot waive — Reintroduction needs a baseline to compare against, and a brand-new account has no logging behind it. The app shows the refusal reason (`baseline_too_short`, `transition_not_allowed`) rather than silently resetting them. Their answer is stored either way, so nothing they told us is lost. ## "The scanner said my cereal bar is red and it's a health food" Read the flagged term back to them. The scanner reads the **ingredient list**, not the nutrition panel, and high-fibre bars are very often bulked with inulin or chicory root, which are fructans. Two entries are deliberately soft: **erythritol** and **natural flavors** are flagged as worth noticing, not as a refusal. An ingredient list Loopa recognises nothing in returns **No data**, not *Compatible*. That is not a failure to answer — it is the honest answer, because an ingredient list says what is present and never how much. ## "The scan gave calories but no FODMAP reading" Check three things in order: they hold **Premium**, they have a **live protocol**, and the product resolved with an **ingredient list**. Not every source publishes one. Without ingredients there is nothing to read, and Loopa does not guess. ## What never happens Nothing in Low FODMAP refuses to log food. Every check and every scan carries **Log as planned anyway**. A ticket that says Loopa would not let them record a meal is a real bug, not the protocol.
