Last week I was debugging a nanoflow that would first retrieve a list of objects -> sync them -> then a validation on the server would show that changes visible in the nanoflow would not be visible in the MF. How you might wonder... well, cached changes in Nanoflows are visible when inspecting, but if these cached changes have not been committed, then the subsequent sync will not push the object changes to the server, and hence the objects on the server end will be empty.
In my case, this problem originated from another issue where sub-nanoflow list changes are not visible in the main flows; basically, my commit lists were empty. I only found out by accident. It would have been really handy to have a state on the objects, just like is the case within Microflows. Please add this state ;-)