CASNext shouldn't trigger infinite loop on server error

Legit server errors updating a value (e.g. E2BIG) would cause CASNext to
think there was a conflict and tell the client to try again, resulting
in an infinite loop.