# Internal Server Error after User is logged out by Admin

**URL:** <https://meta.discourse.org/t/internal-server-error-after-user-is-logged-out-by-admin/79686>\
**Category:** Bug\
**Created:** [February 3, 2018, 12:15am UTC](https://meta.discourse.org/t/internal-server-error-after-user-is-logged-out-by-admin/79686 "2018-02-03T00:15:24Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [February 3, 2018, 12:22am UTC](https://meta.discourse.org/t/internal-server-error-after-user-is-logged-out-by-admin/79686/2 "2018-02-03T00:22:33Z")

</div>

> [@Solarian](#):
>
> This sends off a request to get the latest 5 notifications (/notifications?recent=true&limit=5). Because the user has been logged out, this will fail (403). It seems Discourse (or Ember) will immediately retry this request indefinitely, flooding the server with these requests very rapidly.

I know @sam worked on something related to this recently.

Are you on latest Discourse 2.0 beta 2?

---

_[View the full topic](https://meta.discourse.org/t/internal-server-error-after-user-is-logged-out-by-admin/79686)._