Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 157 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

This has happened to me 4 times in the past hour, on two different machines. Both on normal posts and in what appear to be clearly audits.

When going through the "Low Quality Posts" queue, if I click 'Recommend Deletion' , I get a 404.

BEFORE: enter image description here

AFTER: enter image description here

If I click 'looks good' it works fine, although the only way I could prove it was by intentionally failing an audit: enter image description here

share|improve this question
Just tried a LQ review - got a 404. Never got that before. Triggered by this answer, which isn't (apparently) an audit. – Michael Petrotta Apr 5 '13 at 1:09
I was JUST coming to report this.. – ɥʇǝS Apr 5 '13 at 1:11
@MichaelPetrotta / Seth glad it's not just me... – p.s.w.g Apr 5 '13 at 1:15
I just wanted to add, this has happened again on another review item, so it wasn't just one specific item. – ɥʇǝS Apr 5 '13 at 3:27
@Seth for me at least it happens on every review item in the "Low Quality Posts" queue. (at leasts the ones I click "Recommend Deletion" for) – p.s.w.g Apr 5 '13 at 3:37
This is still a problem, happened to me several times in the last 30 minutes. The items do not seem to get out of the queue as I have had at least 2 of them multiple times. – Anthon Apr 5 '13 at 6:20
it's probably my fault will take a look in a couple hours. – Sklivvz Apr 5 '13 at 6:40
@Sklivvz: Not sure if that helps, but although I have the same problem multiple times on the same post, after 3-4 times they don't seem to pop-up any more. Maybe not everyone has the problem and/or moderators are able to remove these from the queues – Anthon Apr 5 '13 at 7:50
up vote 14 down vote accepted

I had inadvertedly removed a return false; from a JavaScript continuation in a previous unrelated patch… I've fixed it now.

It will be rolled out in the next deployment.

share|improve this answer
1… looks like the same issue, should also be status-completed – Mad Scientist Apr 5 '13 at 12:00
Thanks, I'll accept as soon as I confirm it's working again. – p.s.w.g Apr 5 '13 at 12:10
@p.s.w.g - No need to confirm. If SE Employee mark the question as Status-Completed then it will be implemented/fixed from the next build. :) – hims056 Apr 5 '13 at 12:19
Should be out now. – Sklivvz Apr 5 '13 at 12:26
Tested it on both audits and normal posts - works fine :) – p.s.w.g Apr 5 '13 at 13:01

You must log in to answer this question.

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