Acumatica might want to reconsider it’s use of rate limiting for the API. What exactly is achieved by this?
I have found that logging in and out programmatically in-between calls(synchronous) solves any problems like this, including if you only have a single user.
But honestly, what is Acumatica incentivizing here with this strategy? Making API based calls to the database flaky so that systems don’t work right and customers get mad and move to a different product? What are they worried about? If you had unlimited REST API calls, maybe you could build your own front end and not have to pay Acumatica? Does anyone think that’s going to happen?
What is the strategy here? Licenses are tied to REST API calls, and therefore we’ll incentivize the purchase of more licenses? Why not just sell an appropriate number of concurrent REST API licenses, and then customers can decide what they need, rather than this opaque and error prone system?