When editing a recurring event it can occur than the POST call (the one that creates the exception) finishes well, but the PUT one fails. In this case the exception is created but the new event is not created, causing that the final user thinks that the event disappeared (and causing an inconsistency in database).
It would be great if the scheduler could be configured to make one single call with the data of the master event and the new one in the same post, atomicly.
Moreover, if it is needed to perform remote validation when resizing or moving one event of a serie (the same scenario as the previous one) it would be much more easier to do it with that single call model.