Discussions
Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
Intelligent Payment Automation, powered by BILL (aka Bill.com), lets you automate payments, manage vendor details, and bank account information within NetSuite.
The SuiteApp is available to organizations based in the U.S. with a valid U.S. address, or to global customers (except Canada, China, and Japan) with U.S. business subsidiaries. It only supports payments to vendors operating in the United States.
For more information, visit this thread.
Only one request may be made against a session at a time
During development I encountered this error:
com.netledger.dto.v2_0.faults.InvalidSessionFault: Only one request may be made against a session at a time
Fine. So I put all NetSuiteService requests behind locks. And it still (randomly) happens. I even print out when each thread entered and exited the NetSuiteService code:
THREAD 21399 ENTERED LOCK
THREAD 21399 LEFT LOCK
THREAD 11932 ENTERED LOCK
THREAD 11932 LEFT LOCK
THREAD 25188 ENTERED LOCK
THREAD 25188 LEFT LOCK
THREAD 23367 ENTERED LOCK
Unless I'm insane, it's just you, Thread 23367. I don't know what your problem is.
Where is this exception getting thrown from? Is this NetSuite's servers responding too slowly? I'm tempted to just throw an arbitrary Thread.Sleep() after each request, because I've just about had it with this API.