Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Update: Narrative Insights has been restored and is now available.
Narrative Insights is Temporarily Unavailable due to an Infrastructure Issue. Learn how This Impacts Your Account and What to Expect While the Feature is Disabled.
Narrative Insights is Temporarily Unavailable due to an Infrastructure Issue. Learn how This Impacts Your Account and What to Expect While the Feature is Disabled.
Getting too many Concurrent Session Errors
While we were investigating a customer issue with a unit test we found that the getCustomization() call was taking a long time to complete, and would eventually time out. If we restarted our unit test we would get a concurrent session fault from NetSuite.
For now, we get around this problem by waiting 10 minutes or so for the first sesion to expire, and then we run our unit test again. We generate a new session ID each time we run a unit test, and we thought that NetSuite web services ends the first session if a new session comes in with a different session ID. Is there a workaround for this issue?
0