New Projector Rate Limiting Behavior Rollout Plan

New Projector Web Services (PWS) Rate Limiting Approach

As Projector and our clients continue to grow into even larger organizations, we felt it was time to revisit the approach we take to rate limiting our Projector Web Services (PWS) to make it easier to understand and implement when using PWS. You can go to this link(link will be added here when Stephan’s part is complete) to get a more detailed explanation of how our new rate limiting approach will operate and how different PWS calls will be weighted.  Below is the phased rollout plan to avoid any disruption you may encounter with PWS. 

Phase 1:

During the first phase of the rollout your installation will have the Rate Limiting Mode setting defaulted to “Warning”. In this mode, web service calls will still complete successfully, but they will also return a warning if you are running into the new rate limits. If your current code routinely responds to warnings from Projector Services, please note that these warnings will now include these new Rate Limit warnings.  It is unlikely but possible that this could have adverse effects on your integration, and you should audit your existing code accordingly. Once you have made the necessary code changes,  you can choose to change the Rate Limiting mode to “Error” and you will not need to worry about the next two phases.  For customers with Sandboxes the best option might be to first test out this setting in your Sandbox installation.

Phase 2:

During the second phase of the rollout, your installation will have its Rate Limiting Mode setting defaulted to “Error”.  In this mode, web service calls will fail once they have exceeded the rate limit, requesting that you retry the call after a certain amount of time has elapsed. If you have not yet made the necessary changes to your code, you will have the option to go into the Management Portal and set your Rate Limiting Mode setting back to “Warning” until you are able to make the necessary changes.  You will need to make these changes before we move to Phase 3 or your web service requests will have the possibility of failing.

Phase 3

During the third phase of the rollout, your installation will have its Rate Limiting Mode set to “Error”, but this time you will not be able to change the setting. Just like in the second phase, if your requests are hitting the rate limits , they will not be processed and will respond with a rate limit error.  If you do not have the proper code in place to handle these rate limit responses and retry the web service call, you run the risk of unreliable interactions with Projector via web services.