...
In the case of an error, there will be an exception triggered with a PWS Fault. The violation details will be bundled within the PwsFault in a PwsMessage of type “Error”.
For a list of PWS Web Services and their associated weight classes/hits, please view:
Legacy Service Responses
For the responses to Legacy Services, when a Rate Limit Violation is encountered, the Error Code that is raised is similarly “RequestExceededRateLimit”. This is true whether or not the violation triggers a warning or an error in the response.
...
In the case of an error, the service will respond with the Result of “Fail”, and the Severity of the Error will be marked “Error”.
...
For a list of Legacy Web Services and their associated weight classes/hits, please view:
| NOTE: CURRENTLY, ALL RESTFUL SERVICE INVOCATIONS PIGGY-BACK ON THE PwsGetReportOutput SERVICE, WHICH IS MIDWEIGHT AND COUNTS FOR TWO HITS. |
When writing code that consumes Projector Services, you may want to test or simulate the situation where you are exceeding established rate limits so that you can test the code you have written to handle those limits. A new PWS Service, PwsTestRateLimiter, is now provided for that purpose. You can use this service to artificially increase hits within the current rolling window so that your test may include how your code responds to rate limit errors. PwsTestRateLimiter may also be used to return current parameters in use, and the current hit counts in play.
...