The issue was resolved and operations are back to normal.

Google engineers are investigating the problem internally, from the user reports it still seems to be a backend issue with Google Cloud.

Some actions such as cloning landscapes or creating versions may result in an internal server error. This seems like an underlying issue with Google Cloud Firestore and is being investigated by a Google.

https://github.com/firebase/firebase-admin-node/issues/2345