Resolved New PM that I can't mark as read or delete

[VCeXpedition]

I've got basically the same thing... dated Jan 1, 1970.

https://www.overlandbound.com/forums/conversations/2863/


Dan.

 

[Wawa Skittletits]

View attachment 92609

Any help on this @Michael?

 

[Michael]

Still in progress.

M

 

[Steve]

Mine's back to showing as unread every time I get on the forum, so whatever changed before was only temporary.

 

[Steve]

@Michael Any update on this? The null PM still shows as unread two months on, both on the mobile app and on my desktop. No way to mark as read or delete it.

 

[Jim SoG]

Top

 

[1Louder]

Same issue, https://www.overlandbound.com/forums/conversations/3019/

 

[Michael]

This should be resolved as of today - are those empty conversations gone?

 

[1Louder]

This should be resolved as of today - are those empty conversations gone?

Mine is still there.

 

[Michael]

Mine is still there.

Can you click on it (even though empty) and give me the url in your browser?

Thanks!

M

 

[1Louder]

Can you click on it (even though empty) and give me the url in your browser?

Thanks!

M

https://www.overlandbound.com/forums/conversations/3019/

 

[Michael]

https://www.overlandbound.com/forums/conversations/3019/

Perfect. Thank you.

 

[Wawa Skittletits]

Mine continues to loiter.

 

[Steve]

@Michael No change. Still there and flagged as new.

https://www.overlandbound.com/forums/conversations/2353/

 

[Jim SoG]

Steve was this resolved? I had similar issue and it has gone away.....

Jim

 

[Steve]

Steve was this resolved? I had similar issue and it has gone away.....

Jim

Nope. Still marked as unread. Still can’t delete it or interact in any way.

 

[Jim SoG]

Nope. Still marked as unread. Still can’t delete it or interact in any way.

@Michael

Jim

 

[Steve]

@1Louder and @Wawa Skittletits have the same null message

 

[Jim SoG]

@1Louder and @Wawa Skittletits have the same null message

@Michael

 

[1Louder]

@1Louder and @Wawa Skittletits have the same null message

Mines gone.. It was fixed a couple of weeks ago.