Comment 7 for bug 1864624

I also encountered the same problem. Due to asynchronous reasons, although a successful message was returned after the shelved operation, an exception has actually occurred, and the status of the instance is still paused. I also think this is a bug.