Come on: that’s easily fixable if the provider cares: just assign an ID to every mutation operation. Never repeat the operation if called again. In the real wo

Come on: that’s easily fixable if the provider cares: just assign an ID to every mutation operation. Never repeat the operation if called again. In the real world even bigger players such as AdWords would time out on our bulk requests to them if making >100M changes, without giving any errors back (the jobs just simply tend to disappear; or the jobs never get submitted in the first place). Truth is, you may or may not be discussing the appeal of the REST; but the issue in this context is solved already - and it’s only a matter of professionalism and therefore, the resources required to build something that just works. But in the real world we get stoned students writing the majority of the APIs; having read a few how-to’s.