# Moderator move post, get 500 internal error, how to troubleshoot

**URL:** https://meta.discourse.org/t/moderator-move-post-get-500-internal-error-how-to-troubleshoot/128328
**Category:** Support
**Created:** [September 11, 2019, 8:23pm UTC](https://meta.discourse.org/t/moderator-move-post-get-500-internal-error-how-to-troubleshoot/128328 "2019-09-11T20:23:03Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![Remah](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/remah/32/70590_2.png) [@Remah](https://meta.discourse.org/u/Remah)
#### Post date: [October 2, 2019, 12:25pm UTC](https://meta.discourse.org/t/moderator-move-post-get-500-internal-error-how-to-troubleshoot/128328/5 "2019-10-02T12:25:06Z")

</div>

> [@DiscourseMetrics](#):
>
> posts are not being marked as read

This resolved bug probably explains the unread states:

> [@Topics incorrectly stuck in unread state on Android in Chrome 77](https://meta.discourse.org/t/topics-incorrectly-stuck-in-unread-state-on-android-in-chrome-77/129907):
>
> Per: [Unread tab does not update after reading](https://meta.discourse.org/t/unread-tab-does-not-update-after-reading/129162) There were quite a few people mentioning issues with topics not being marked read on Android. We have done some root cause analysis and found that the page visibility api changed the way it operates in Android Chrome 77. It was discussed in brief here: [https://github.com/pgilad/react-page-visibility/issues/9](https://github.com/pgilad/react-page-visibility/issues/9) There is a fancy graph that explains the new lifecycle here: The symptoms of the issue is. You use your android You flip to do som…

---

_[View the full topic](https://meta.discourse.org/t/moderator-move-post-get-500-internal-error-how-to-troubleshoot/128328)._