Some Calais errors make sense to do a retry later with exactly the same content and params like:
Calais Backend-Server is Busy. Please try again later.
Other Calais errors definitely do not make sense to do a retry later with exactly the same content and params like:
paramsXML is invalid.
Of the documented error messages (http://www.opencalais.com/documentation/calais-web-service-api/error-messages), it seems that various Backend-Server error messages are the only ones that make sense to do retries without the need to change something in the request. But I also notice that not all error messages that I get are documented at the above url.
Can we have an (evolving) definitive list of the Calais error messages? Can those that make sense to do unmodified retries be noted as such?

Such errors are generated by Mashery (our api provider). You should see a simple XML response similar in the format of
<h1>Code Message</h1>
Here are the possible error messages with their codes.
403 - Over Queries Per Second Limit
403 - Over Rate Limit
403 - Service Over Queries-per-Second-Limit
503 - API Maintenance/Service Unavailable
So the possible XML responses I can expect are of the following forms
(1) <!--Use of the Calais Web Service is governed ... etc. - giving a valid RDF response
(2) <Error Method=... etc. - giving a Calais error
(3) <h1>Code Message<h1> - giving an api provider error
Is that right?
Yes, correct. Those 3 cover the possible responses.
sumit
Thanks!
Hi John,
The list of backend errors on the Errors page is complete. However, we use Mashery as our web service provider and you may be seeing some rate related errors from them. Our allowed daily limit is 50K/day and 4 docs/second. If you exceed the limit you should see '403 - Over Queries Per Second Limit' errors.
You client should re-submit docs for these 403 and the 'Calais Backend server is busy' messages only.
Hope this helps.
sumit
Thank you. That is very helpful.
I have not been able to reproduce the '403 - Over Queries Per Second Limit' errors. Can you give the exact xml I should expect when this error occurs?