@CTO.care Thanks for sharing the details in private message. I had a look at the backend logs and I could see the 200 status succeeded message.
So this was a transient issue and the deployment did succeed in the background. The conflict error message was due to the resource successfully created previously.
If you wish to perform any deployments again, please feel free to test again.
**
Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.