Faced the same issue. What I did was: I made sure I fixed the Ambiguous Identifier locally and created a new Private Version, then reverted the published map to a previous version, one without any errors. That let update the map to the newest private version. This is not a fix and the obvious downside is that presistable data might get lost.
1 Like
I did this but it didn’t work for me.
I can’t revert to previous versions as I have verse persistence in the map, but I’ve republished the same private version, then a new one, but it didn’t work.
Are there updates on the situation? Is there a fix planned for this Wednesday update? 
2 Likes
Hopefully you had a good Thanksgiving if you’re in the States, just coming back to this and while they closed my ticket I wanted to respond to your question on the uproject files. I did remove the experimental tags (or rather set them to false) even though no experimental items were actually set or changed. I Pulled the diff from perforce of what I did, now this also occured during the 37.51 to 38.10 update as well. I see they did put this issue on the Trello board ( Trello ) but it’s not till Q3 of 2026. I do know changes to the uproject file SHOULD trigger a full rebuild as my main issue was that it would not update the files during cook as it would continue to check for files that didn’t even exisit. As much as it sucks to have to just re-publish it might be the only option. If Epic wants us to use Island Codes as Key identifiers then there should be a way (even if it requires a support ticket) to request the old public code be transferred to the replacement island. Hopefully this helps, if I come across anything else I’ll let you know. Good luck 
1 Like
FORT-1011852 is ‘Closed’ as ‘Fixed’. The issue will be addressed in 39.00.
Can confirm it’s working again now! Thank you!