Reproducing Rate Limit Errors on PUT/POST operations

For the first time, we are starting to get rate limit errors on one of our clients using PUT/POST requests in the API, apparently due to the size of the objects and child items they are using.

We have started to implement a handling process for this, as we do with GET requests, but when constructing test data to reproduce the situation, we have been unable to hit the limit in our test environment, even for objects considerably larger than those used by the client.

Is there a way of temporarily reducing the rate limit in our test environment so that we can recreate these issues? Or is there another approach we should be taking to mirror what our client is experiencing?

Customer care should be able to work with you on that for the configurable limits.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.