personal messages issue

I had an issue this morning with my messages. It was resolved by clearing cache & such, but I feel it still needs to be reported because if it happens to others without them noticing, it could cause problems.

I went to reply to a message from earlier. When I opened it, the message contents did not match the sender/subject line. I looked in every message, and except the 1st 2, all others had the message contents from the message above it. The 2nd msg in my list was a co-op message & it had the contents of the message I had sent to the co-op this morning.

So, the 3rd msg in my list had the correct sender of a message, but the contents read what the 2nd msg actually was.

I did a test reply to a message. The reply went to the sender with the subject line of the message I chose to reply to … but the contents of the message I replied to were completely different. Had I thought I was replying to the content message, my reply would have gone to the wrong person.

Just to be clear, here’s an example if my inbox looked like;

Msg 1:  coop msg rec’d about event

Msg 2: coop msg about congratulations

Msg 3 from person A: personal msg about an event

Msg 4 from person A: personal msg about an event

Msg 5 from person B: personal msg about health

Msg 6 from person C: personal msg about an event

Msg #2 showed the contents of what I had sent as a co-op msg, not the actual msg that person sent

The actual contents of what was in msg 2 when it was sent, is now appearing in msg 3 as if it were rec’d from person A

That continues down so that the contents from msg 4/person A is showing in msg 5 as if it was rec’d from person B. And the msg 5 contents are showing up in msg 6 as if they were from person C. 

If I open msg 6 and reply, it will go to person C who sent that msg. But the contents I would be replying to would show the PM originally sent in msg 5. Which means I could be discussing personal health issues with the wrong person.

I could not find a way to do screen shots without showing player names that is prohibited, so I hope this makes sense. Yes, this was all resolved by clearing cache & history, but this could be real issue if it’s not caught in time.