# Feedback on the new Review Queue (2019)

**URL:** <https://meta.discourse.org/t/feedback-on-the-new-review-queue-2019/112837>\
**Category:** Announcements\
**Tags:** new-feature, review-queue\
**Created:** [3월 28, 2019, 4:50오후 UTC](https://meta.discourse.org/t/feedback-on-the-new-review-queue-2019/112837 "2019-03-28T16:50:12Z")\
**Posts on this page:** 1\
**Showing post:** 42

<div class="post-metadata">

**Author:** ![eviltrout](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eviltrout/32/5275_2.png) [@eviltrout](https://meta.discourse.org/u/eviltrout)\
**Post date:** [4월 3, 2019, 7:31오후 UTC](https://meta.discourse.org/t/feedback-on-the-new-review-queue-2019/112837/42 "2019-04-03T19:31:17Z")

</div>

I discovered a pretty big issue today following some bug reports with reviewing users. I was creating the “Reviewable” for a user when the user was created, not when they activated their account. Users can’t be approved until their accounts are active so you’d just see a “Reject” button which was confusing. This commit should fix it:

[https://github.com/discourse/discourse/commit/c1ea63bdc17ca3e7fabb0d857e59e9234bde7da8](https://github.com/discourse/discourse/commit/c1ea63bdc17ca3e7fabb0d857e59e9234bde7da8)

The commit also creates the reviewable asynchronously. Besides being slightly faster for the user activating their account, it gets around a nasty issue of a nested database transaction that I couldn’t recover from 🙂

---

_[View the full topic](https://meta.discourse.org/t/feedback-on-the-new-review-queue-2019/112837)._