We did fix a logic issue related to the revision feature of the endpoint. It was checking if a revision was existing to check if the CRUD: Update endpoint should be used. Since the first time we create a record, no revision are created, then we could re-use the CRUD: Create endpoint on an existing (but not yet revisioned) record. This is now fixed. With this fix, if revisions OR published records exists for a given record URI, then a 312 error will be returned.