Nutrition Glitch

Anyone else experiencing a glitch. My app is saying I’ve consumed over 90,000 mg of sodium today. Which is wrong cause all I’ve recorded was a protein shake(the same one I’ve been recording for the last two weeks).

Replies

  • claireychn074
    claireychn074 Posts: 1,597 Member
    Anyone else experiencing a glitch. My app is saying I’ve consumed over 90,000 mg of sodium today. Which is wrong cause all I’ve recorded was a protein shake(the same one I’ve been recording for the last two weeks).

    Check the entry - sometimes they get mistakenly updated by a user and then you select it unknowingly. There used to be a garlic entry which listed 400 calories for one clove - I only discovered it when a recipe came back with unexpected calories.
  • Alatariel75
    Alatariel75 Posts: 18,211 Member
    It's likely to be an error in the entry you used. The database is largely user-added and prone to errors. I tend to confirm new entries independently.
  • Hobartlemagne
    Hobartlemagne Posts: 548 Member
    Yes- theres a weird ingredient in the database thats all wrong.
    I found garlic somewhere on the database that had this problem
  • yirara
    yirara Posts: 9,933 Member
    Pretty much everything in the database is user-entered. Everything related to salt is probably a mixup of salt/sodium and mg/g
  • springlering62
    springlering62 Posts: 8,411 Member
    edited November 13
    My fave lately is the entry for for powdered cocoa I found: “100 Grams = 1 calories”.

    In my perfect world. *sigh*

    There’s a lot of that type of stuff floating around out there. You have to weed through it and find the one that looks most reliable.

    If I’m adding something new, I’ll scroll through several pages of it to kind of get an idea of where the average falls before selecting a food.