Hi @Zhou Qing 周晴 ,
From the description, seems like it's related to a transient backend incident which has already been restored. So, please have a try on your end again and see if everything is fine now.
If you are the administrator, you might be able to see the EX606690 in the Issue history of the Service Health Dashboard:
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.