Excellent question and one I personally hadn't considered fully in the last few years working with Meraki. The usual conversations I have tend to be an organization where one person/team is managing the Meraki deployment and any updates are run through them OR people who are just being introduced to programmability. I'm now VERY curious as I suspect this scenario could occur with direct dashboard access as well. I'm definitely going to talk to the product team about this as concurrent management is arguably a benefit of SDN.

Off the type of my head, one could build a message queue into their application and add in logic to check for conflicts (though, to your point, that would be a monumental effort to be bulletproof). Post-call unit testing with rollback could be easier, however that would be the best proactive solution.

I'm curious as to the scenario you encountered that prompted the question. If you'd like to share that would be greatly appreciated! If it's more academic curiosity, then thank you and I'll definitely be following up on that (and if I get answers before next Thursday I will address in the webinar)