The suggested edit corrected formatting issues in the code posted by the OP. In the initial post you can see line breaks in the code posted.

Most of the time when someone rejects a suggested edit, a proper reason is given, like This edit is too minor; suggested edits should be substantive improvements addressing multiple issues in the post.. Shouldn't Community also provide some reason while rejecting suggested edits?

Update Another similar example. A reviewer Frank approves and Community rejects (ofcourse without sharing any reasons) !

  • 3
    This is pretty common in the first few minutes of a bad post life. Many users jump on the edit wagon and the first wins. If the first was user with more than 2000 rep, it means kicking any suggested edits out. Frustrating yet that's how it works, so just wait 5 minutes before suggesting your edit. Mar 12, 2013 at 8:36
  • What about The Community (super user) forgetting (by mistake or intentionally) to drop some comment while rejecting the edit ?
    – Apurv
    Mar 12, 2013 at 8:38
  • What comment should it make? It's not an actual user.
    – Bart
    Mar 12, 2013 at 8:40
  • 2
    The "community" user is just a bot, I agree there should be a comment like "Auto rejected due to other edit" but that should be a separate feature request. Mar 12, 2013 at 8:40
  • What about another example stackoverflow.com/review/suggested-edits/1698036 ? No other submitted the edit before mine. The revisions (stackoverflow.com/posts/15356364/revisions) say it was edited by the OP way after my suggested edit was rejected.
    – Apurv
    Mar 12, 2013 at 8:44
  • 1
    @Apurv in this case the OP clicked "edit" before you clicked it and submitted it after you submitted your suggestion, having same effect as before since OP "vote" is binding as well. It's not showing in revisions history as it was within the five minutes grace period. Mar 12, 2013 at 9:45
  • Some research I did into this suggests that waiting out the 5-minute grace period is just better for everyone: meta.stackexchange.com/questions/164802/… Mar 24, 2013 at 4:25

2 Answers 2


Looking at revision history and the timestamps of both examples you provided, one possibility for the reason your edits were rejected was not because you lost an edit race with a 2K user, but you actually lost an edit race with the OP of the questions AND it was within the 5 minute grace period of the edit. The likely order of what happen is something like:

  • OP posts his/her question
  • You click edit on the question shortly after it was posted
  • Shortly after you (or possibly before you), the OP clicks "edit"
  • You commit your edit
  • Shortly afterward, the OP commits his/her edit. Since it is within the 5 minute grace period, no edit history is captured. It still appears as if the original posting is the most recent revision

This scenerio would also explain the time lapse between your suggested edits, the rejection time, and when the next edit was captured in the revision history

Because the OP has a binding vote on edits for his/her question, your edit is rejected by Community (this is a similar effect as if a 2K user reviewed your edit and tried to improve your edit from within the review queue - when this happens your edit is immediately rejected or accepted by Community). But since it was within the 5 minute grace period after the post was made, there was no indication in the suggest edit as to who edited your question after you.

But in general, Community never provides a reason for the reject. Because it does not have the ability to think for itself (yet), it does not know why it is rejecting the edit.


It was probably rejected because it was edited by another user at the same time.


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