This can be caused by sending two back-to-back resize requests. When handling the first, the server may have already replaced the smo key with a new one.
This can be caused by sending two back-to-back resize requests. When handling the first, the server may have already replaced the smo key with a new one.