It could be that you commit the object in the change activity of your new button microflow. The default behavior of the cancel button is to rollback the object, which means deleting the object if it is new (i.e., it has not yet been committed) or rolling back the changes if it is not new. So by setting Commit to 'No' in the change activity, the object should be deleted when you press the cancel button.