gophercloud currently lacks support for proper tracking of revision numbers. That makes it prone to race conditions due to concurrent updates. For example, in the following sequence:

*) client A retrieves object Z
*) client B updates field Z.x
*) client A updates field Z.x with a merge from its cache

Thus, client A can easily overwrite the changes from client B.