Maybe you have xpath constraints in the access rules of the entity that prevent records from being read/write after creation. Another time I have seen this behavior is when permissions are left out and the object makes a roundtrip to the server and back to the client thereby the security is checked again and the error will be shown as the user does no longer have permissions on the attribute. To solve this investigate the access rules set for the entity and as it is not a conssistent error probably there is some micro/nanoflow involved in changing attributes under specific conditions.