In rare occasions, the servers get busy and sometimes fail to finish the merge in time and so it gets reported as failed. Could you please try to refresh your tab and merge again to see if it goes through this time. If not, please let us know and @zpaul will investigate bit later today.
We have just deployed some changes to our backend that might affect the issue you are experiencing. If you are still unable to merge correctly (after restoring to a valid checkpoint first) we will have our team investigate but you might have to wait until our LA team comes online later today.
Hi @karin, we have just deployed some changes that will likely prevent things like that happening again. Similar to git, to “redo” a merge one would need to create new branches from the checkpoints before a bad merge and merge them. This is to avoid the common ancestor checkpoint created by a bad merge.