Hi Joanna, and thanks for the feedback! Fortunately, our team has already found and fixed this problem. If you upgrade to ArcGIS Pro 2.7 you should not come across this error again. If you do, please feel free to let us know so that we can further investigate what's going on.