The specified pop receipt did not match RRS feed


  • I believe this to be an optimistic concurrency failure. The following is documented for the delete message operation:

    -- If a message with a matching pop receipt is not found, the service returns status code 400 (Bad Request), with additional error information indicating that the cause of the failure was a mismatched pop receipt.

    Each time a message is retrieved it gets a unique pop receipt. When performing a delete, if the pop receipt is not the current pop receipt then a mismatched pop receipt error is issued. This could be caused by a message taking too long to process and its visibility timout expiring allowing the message to be retrieved again with a new pop receipt invalidating the original one. An attempt to delete the first message with its old pop receipt will fail.

    • Marked as answer by Wenchao Zeng Thursday, September 1, 2011 8:47 AM
    Tuesday, August 23, 2011 10:18 PM