The only other thing that could be causing it, that I know of, would have to do with when in the load/initialization of WP the update occurs. If the update is happening before ACF is initialized then this could have unexpected results. This is also the case with any calls to ACF functions.
