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.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Update your Profile with your Support type to get your Support Type badge.
Don't miss out on our Question of the Week! You only have until tomorrow, October 23, 2025, 2PM ET to comment your answers and earn rewards! Click here for more details.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more
WebServices connection timeout exception
We have been using Web Services version 2.5 for quite some time. All the time, our integration system is running smoothly and able to retrieve our data without any issue.
Previously, our system trying to retrieve “Sales Order” or “Invoice” data it might took up to 2 hours to complete means NetSuite web services session can last for more than 2 hours. But started from mid of September, our integration system hit the connection timeout exception. This exception occurred when our system trying to query data for more than 15 minutes and our system halted. FYI, we did converted our NetSuite web service to the latest version 2011-1, but unfortunately even the latest version couldn’t work , the same exception still happened.
0