When setting up a new pod or updating it in 18.104.22.168, if you updated an individual field and then clicked Save Pod, the field was automatically updated. Now, if you do not click Update Field first, then your changes are lost. There is no warning that this will occur.
This has bothered me for a while, too. A warning would suffice; the behavior is by design, otherwise. All changes to that field are effectively "buffered" until you click update field.
However, I'm going to re-label this as an enhancement and move it to 2.2 in favor of bug fixes in 2.1.x right now.
We'll change how this works for 2.4 when I rebuild the field manager in #799 and #109