My settlements are constantly listing broken numbers in the Data tab of the Pip-boy, and experiencing significant negative penalties to happiness, regardless of the actual numbers.

When I return to that settlement, the numbers temporarily update to the correct values. If I leave right away, they switch back to broken numbers. Usually the number is 0, but other low numbers are occasionally the case. This affects all settlements except the one that has only ever had a single construction phase. The more frequently that a settlement has been updated via workshop, the more frequent and severe the bugs are.

At this point of my first playthrough, here's all I've managed to sort out about it:

- It seems to begin the first time a settlement has a second construction phase, especially if any existing assets were deleted/replaced. Generally, the lower values seem to reflect the lowest numbers that occurred during the deletion of assets. For example, if I had 14 beds in Sanctuary Hills, and then I deleted 12 of them, replacing them with higher-value beds, the broken value would register as 2 - the lowest number of beds ever registered in Sanctuary Hills. For some reason, it will not properly update this number to the new value (14) except on rare occasions while the player is actually in Sanctuary Hills. This issue seems consistent across all resources, including food, power, and water.

- The problem seems to stabilize over time, but never goes away completely. If it has been a long time since the last construction/deletion, the settlement tends to put forward mostly correct values most of the time, but still occasionally reverts to the lowest registered values.

- The only temporary workaround I have is to return to the settlement, and either engage in further construction, repeatedly rest for different periods of time until the values update/change, or a combination of both. This seems to adjust the values to the current, correct numbers, for a variable period of time. In all cases, any settlement that has experienced the bug will eventually experience it again (although, as mentioned above, the frequency decreases over time if no construction updates or asset deletions occur.)