When reviewing Low Quality Posts, I accidentally pressed Skip instead of Recommend Deletion. So when I noticed my mistake, I went back by pressing the browser's "go back" button. The problem is that now the item is not reviewable:

enter image description here

After some testing, I've figured out that it seems to happen every time I press Skip and then visit the review item again, either by pressing the browser's back button, following a link from my review history, or visiting that URL in any other way. However, refreshing the page or even closing the tab and then copy-pasting the URL into a new tab works just fine, so it seems to only happen after having pressed the Skip button.

Here are two examples where it happened:

This happens only with the Low Quality Posts queue; in other review queues, I can still review an item by navigating back to it after skipping it initially.

Can this bug please be fixed?

  • 2
    Cross-site dupe Commented Feb 20, 2017 at 19:27
  • 7
    This bug is really annoying, since it encourages us to avoid skipping any review we think we might ever want to complete. I would be surprised if this weren't leading to numerous bad reviews. Whether unintentional or by design, the inability to return to a LQP review item we've skipped encourages us to behave irresponsibly while reviewing. Commented Sep 15, 2017 at 21:08
  • I've found a way to work around this. Go to the review that you skipped, right click on the Next button, and select Inspect. Then the browser's developer tools will appear. In the developer tools, you will find somewhere where it says <input type="button" value="Next" title="review next item" data-result-type="254">. Change 254 to 7 for Looks OK, 5 for Edit and 9 for Recommend Deletion. I did that here and it worked, but it would still be nice if this bug could be fixed. Commented Feb 11, 2018 at 8:26
  • Using the back button mess up JavaScript code that was executed before pressing it. Since the review use lots of JS, it's expected to break. Commented Feb 11, 2018 at 12:09
  • 9
    @ShadowWizard It's not only the back button that does that. It also does that if you skip and then go into your review history, check the "show skipped reviews" checkbox, and then follow a link from there. It has nothing to do with the back button. Commented Feb 11, 2018 at 12:13
  • 1
    I noticed that Low Quality Posts reviews have a different behavior than the other queues; once you've had a look and closed the tab / gone elsewhere there's 'no going back' (without some persistent messing around). The other three queues don't lock you out like that.
    – Rob
    Commented Oct 26, 2020 at 21:17
  • This has regressed. Commented 5 hours ago

2 Answers 2


This will be fixed in the next build.

Each queue has a general filter to exclude non-skip reviewed tasks when picking new ones, but a handful of queues have cross-validation on post ID. The apparent thought is that we don't want the reviewer handling the same post in multiple queues. (For example, the same post could end up in First Posts and Late Answers.) Unfortunately, this additional exclusion logic treated skipped tasks as reviews and prevented them from being returned to.

  • 6
    Brian, at MSO they complain here about strange behavior of skipped reviews in LQ queue, could this be a side effect of recent change?
    – gnat
    Commented Jul 29, 2021 at 9:35
  • 1
    Still broken as of 7/29/2021 15:36 Zulu. It's impossible to skip a review item.
    – Ramhound
    Commented Jul 29, 2021 at 15:36
  • 1
    above issue looks like also reported over here at MSE: Skipped Review Tasks Showing Again
    – gnat
    Commented Jul 29, 2021 at 18:57

We're taking a look at this as part of ongoing work on the review queues. So far, it is unclear whether this behavior is intentional or an oversight. I'm hoping we'll be able to dig up some history internally, but unless we come up with something absolutely showstopping, I expect we'll be fixing this.

We'll post an update here once we have a decision either way.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .