Sharon, just to introduce myself. My name is Jim Jones, I’m a senior software engineer at Zvents (recently acquired by StubHub). We’re located in San Mateo, CA.
I am the author of the Ruby/Mechanical Turk integration gem, Turkee ( http://www.github.com/aantix/turkee ).
Recently I’ve run into an issue with the platform’s externalSubmit interface. I’ve posted the specifics here :
https://forums.aws.amazon.com/thread.jspa?threadID=84581&tstart=0
My frustration lays with the fact that there is no way to accurately debug issues that arise with posting to the externalSubmit interface. All I receive is an ambiguous “Your request was not completed successfully”. This isn’t the first time I’ve run into this ambiguous error message.
Further complicating the issue, the above issue appeared to be inconsistent on my day-to-day debugging. One day it appeared to be length dependent, the next day those same long form name variables were accepted.
Other users have expressed frustrations similar to mine with debugging the externalSubmit interface.
http://aws.amazon.com/code/555
> Not only does this method provide no feedback on what
> went wrong, it is nearly impossible to debug. Don’t waste
> your time on this.
https://forums.aws.amazon.com/thread.jspa?threadID=34880
> All fixed (though a debug mode would be appreciated).
In closing, I’m advocating the following :
1) A debug console for the externalSubmit interface that will provide detailed error messages when an external form submission has failed.
I want to further enhance my Mechanical Turk gem but at this point, I’ve wasted so much time debugging ambiguous errors that it’s becoming harder and harder for me to justify donating my time to this platform. Please convince me otherwise.
Respectfully,
Jim Jones
http://www.github.com/aantix