Why your TDEE is not updating in Zolt

When Zolt holds your TDEE, it keeps the current estimate instead of publishing an update from recent data it cannot use confidently. This is usually a data-quality or connection issue, not a broken calculation.

Start with the status shown in the TDEE area. It identifies the kind of information Zolt is waiting for.

Quick checks

Work through these in order:

1. Confirm that recent meals are logged, including weekends.
2. Check that you have recent weigh-ins.
3. Mark partial nutrition days as Skipped instead of leaving them incomplete.
4. Use Fasted only when the low intake was intentional and complete.
5. Confirm that the expected nutrition and weight sources are still connected.
6. Check for duplicate or conflicting sources.

Once the recent record is consistent again, leave the target alone and let Zolt reassess it. Repeatedly changing the goal does not repair missing data.

Missing nutrition data

A day can look complete because it contains breakfast or lunch even when dinner was never logged. Check the whole day, especially restaurant meals, drinks, and weekends.

If the day cannot be reconstructed accurately, mark it Skipped. Do not enter a guessed total simply to fill the gap. Handling incomplete days covers the available statuses.

Missing weight data

One weigh-in can move sharply because of water, sodium, digestion, or training. Zolt needs a continuing record to separate that movement from the underlying direction.

Check whether your scale or health platform is still writing weight data. If you enter weight manually, confirm that the entry appears on the expected date.

A source stopped syncing

Open the connected-data settings and confirm that Zolt still has access to the source you expect. Platform permissions can change after an operating-system update, device replacement, or app reinstall.

If more than one app writes the same kind of data, check which source Zolt is reading. Duplicate nutrition or weight records can be as disruptive as missing records.

Read Connecting nutrition and weight data for source setup and conflict checks.

A week was genuinely unusual

Travel, illness, medication changes, a large change in training, or several untracked meals can make a recent stretch less representative. Correct mistakes you can verify, mark incomplete days honestly, and return to your normal logging pattern.

Do not change old entries just to make the TDEE number move. The record should describe what happened.

If it still does not update

Compare the status message with your recent nutrition and weight history. If both are present, complete, and connected but the status still appears wrong, contact support with:

• a screenshot of the TDEE status;
• the dates affected;
• the nutrition and weight sources you use; and
• whether either source recently changed.

That is enough context to investigate the problem without sharing sensitive health data in the first message.