This is the full checklist to diagnose and address these errors due to the NetSuite governance model.
Here are the most common steps to diagnose and fix this type of error:
- Contact NetSuite to determine how many concurrent requests are allowed for your NetSuite account.
- Open every individual NetSuite connection record in your integrator.io account (for your production account only) and check the RESTlet Concurrency Level field in the Advanced Section (ignore the Web Services Concurrency Level field).
- The sum of the RESTlet Concurrency Levels across all the different connections for the production NetSuite account must be less than or equal to the value allowed by NetSuite.
If you are still seeing the error after going through the common steps above, then we need to go a level deeper to understand what else is running in your NetSuite account.
- Are you running our NetSuite + Salesforce SmartConnector? If so, then you need to escalate to NetSuite that you need an extra SuiteCloud+ licenses to avoid this problem. Currently the NetSuite + Salesforce SmartConnector supports real-time point-to-point communication between Salesforce and NetSuite, and we cannot control how many concurrent requests are sent from Salesforce to NetSuite. The best short term solution is for you to get more SuiteCloud+ throughput. We are working on a longer term solution that will use middleware to queue data and control the concurrency.
- Using other integration products?
- Do you have any other integrations running that were built by another company? If so, then you need to work with that company to understand concurrency requirements and then adjust concurrency limits across all integration products accordingly.
- Are you using any productivity type products (Gmail sync, SmartClient or other partner productivity products)? For these type of products, there is no way to guard against concurrent requests, and you need to escalate this to NetSuite support so that NetSuite Product Management can be made aware of how their new changes are affecting business operations. If you can pass the support cases to us as well, we can help escalate where possible. We can not log cases on your behalf, and it is important for you to directly discuss this with NetSuite.
- If are are not sure about the above two points, scan your NetSuite account for any RESTlets that are actively being used, and if there are any, you should contact the author of the RESTlet to understand usage patterns, and then go from there.
- Are you using one of our older Java integrations? If so, then we can tell you the concurrency level needed by that integration, so that you can then adjust your concurrency level fields accordingly everywhere.
Please sign in to leave a comment.