Internal Server Error during review submission causes review to be processed but email to be unsent


Status Graveyard
Admin/Editor Tools
7 years ago
2 years ago


(Reporter: kmag, Unassigned)


4.x (triaged)


(Whiteboard: [ReviewTeam], URL)

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:6.0a1) Gecko/20110419 Firefox/6.0a1
Build Identifier: 

I'm not sure what can be done about this or how often it happens. I only found out by accident when I mentioned an author's review to him.

I submitted the review for the attached URL and got an Internal Server Error page. I reloaded the page to resubmit and got a message that there was no review pending. The review was already in the log from the first submission, but apparently the email never went out.

As there's currently no way for an author to view his past reviews, this is a major issue. It means that for some reviews which we think were successful, the author has no notice of the status of his review, or more importantly, of our feedback. Review submission should either succeed fully or fail fully so that we can re-submit. It shouldn't leave us with a partially processed review and no means to rectify it, or even any knowledge that we need do so.

Reproducible: Sometimes
Ever confirmed: true
OS: Linux → All
Priority: -- → P2
Hardware: x86_64 → All
Whiteboard: [required amo-editors]
Target Milestone: --- → Q2 2011
The traceback says:  

>  SMTPServerDisconnected: Connection unexpectedly closed

I assume they had some unexpected downtime, as I've never seen it before.  We can catch this error and log it and try to resend, but it's not something that regularly occurs.
Target Milestone: Q2 2011 → 4.x (triaged)
Reclassifying editor bugs and changing to a new whiteboard flag. Spam, spam, spam, spam...
Whiteboard: [required amo-editors] → [ReviewTeam]
This might have been a fluke, or an old bug. Please reopen if it happens again.
Last Resolved: 5 years ago
Resolution: --- → WORKSFORME


2 years ago
Product: → Graveyard
You need to log in before you can comment on or make changes to this bug.