Hello @Pete Luetchford - Thanks for reaching out and posting on the MS Q&A!
The short answer is that the message ID will have changed to a different GUID when you access the message again from the poison queue.
As you've probably already read on the doc, after all five attempts fail, the functions runtime adds a message to a queue named <originalqueuename>-poison. While looking at the implementation of this operation in the code, I found that the HandlePoisonMessageAsync()
method passes the message.Body
(which is the string content of the message) to the AddMessageAndCreateIfNotExistsAsync()
which then calls AddMessageAsync()
method that'll create a new message, which will have its own GUID assigned for message ID, on the poison queue.
I also tested it locally and was able to confirm the same behavior as well. I hope this confirmation helps, please let me know in the comments section below if you have any further questions on this one.
Please consider contributing to MS Q&A by marking 'Accepted Answer' and ‘Upvoting’ as applicable.