Since the CMIS protocol is a stateless protocol, each request creates its own transaction. Therefore, it is up to the developer to manage rollbacks when several operations should be part of one logical transaction. So, for example, if you create three folders and one file, and want all of these calls to be part of one logical transaction and succeed or be rolled backed so that the system is consistent, then the rolling back logic has to be written by the developer. Therefore, for example, if creating the third folder fails, the first two folders that were already created must be removed automatically.