I encountered a problem when i tried to merge branches using devops, it came with a error message said:
The server ‘@cloud’ has a not valid format. The server valid format is: [protocol://][organization@]server
Then i found a verified solution and tried to implement it:
but I found out when I click Save button according to the step it said, there’s no reaction whether how many times i clicked it.
Why did that happened and how should i solve it ?
(Please save me)
You should wait for a moment or just try serveral times. I also encountered it.
Click the Custom and back again to Default, then it should work.
That didn’t work for me 
Same problem, and didn’t work here either…
Same issue. Every time I click “Save” this pops up in the Console, weird.
Same problem, difficult to use…
Thanks for bringing this to our attention. The team is currently investigating the issue and will report back here when it’s resolved.
I’m glad to report that a fix for the issue has been deployed and saving using the “Default” option is now working as expected. Our apologies for any inconveniences caused by the issue.
cc: @slimebutter4321 @orangeshua @Nathusan @Oelson @Cloudssss
Thank you so much for all your hard work on this! While the immediate issue is resolved, I wanted to let you know that the underlying problem with merging branches through DevOps still seems to be happening. I’m still encountering this message:
The server ‘@cloud’ has a not valid format. The server valid format is: [protocol://][organization@]server
Just wanted to mention this isn’t urgent at all - I completely understand this initial report wasn’t meant to cover everything. I’ll add more details under the original post whenever convenient. No rush whatsoever, but whenever your team has bandwidth to look into this someday, I’d be so grateful! 
Hi @slimebutter4321,
Just to confirm, where are you seeing this error? Is it happening on the Build Automation Settings > Source control tab like in your screenshot?
Because with your “merge branches using devops” text, I think of the DevOps > Version Control > Repositories > [a specific Repository page] > Branches tab.
Could you provide a screenshot of the page you’re on with the error message? (and feel free to blur anything else). This will help with our investigation.
Thank you!
Thanks for sharing the screenshot @slimebutter4321. The team is currently investigating the issue and will report back here when it’s resolved.
HI @samssmurfff,
Thanks for bringing this to our attention. The fix for this has been deployed and you should no longer see a flicker of “Unsaved changes” after clicking “Save” button. Thank you!
Thank you for the fix. I haven’t tried and tested as me and my “team” have swapped to git as suggested by the community. But we appreciate the support regardless.
Hi @slimebutter4321, I checked your last message. It looks like a different error than the one originally reported in this thread. I can see there was a problem when saving some data in the web dashboard for Build Automation.
Checking your last screenshot, it seems to be a problem in the Plastic GUI when running a server-side merge. Can you attach the Plastic client logs and the following configuration files?
C:\Users\xxx\AppData\Local\plastic4\logs
C:\Users\xxx\AppData\Local\plastic4\client.conf
C:\Users\xxx\AppData\Local\plastic4\profiles.conf
You can also open a support ticket with us at devops-vcs-support@unity3d.com
Thank you for raising the issue to begin with! Even if you’ve transitioned to Git, please know that we’re here to support you whenever you need it. Your feedback is appreciated, and it helps us continue improving for everyone. Don’t hesitate to reach out if you ever decide to revisit or have any questions in the future. 
I’d be glad to help! 
Here’s the zip file with the packed data you requested:
DevOpsBugReport.zip (10.3 MB)
Blockquote
I did my best to filter through the logs to avoid sending complete files that might create extra work for your team. However, it appears the system didn’t generate any logs during that specific timeframe when I triggered the bug (´･ᴗ･`). So here’s the whole log file ~
Hi @slimebutter4321, I’m afraid I can’t find the error in the logs. Can you force the error again and let us know the time it happened so we can find it in your logs.
What are the steps to reproduce the error? Does it happen when you try to run any server-side merge via the Plastic GUI or does it happen only sometimes?
I can see that you are using a @cloud.cn UVCS org, which may be relevant to reproduce the issue.
