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.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
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.
Share Your SuiteWorld Experience & Earn a Special Badge!
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
Why throwing an error in Async entry point Function gives unexpected error?
Has anyone had an issue using the async
keyword in entry point functions such as post
or get
in RESTlet script types?
Our team has noticed that if you make a entry point function like post
async, it results in an unexpected error if you throw anything. For example, the simple script below, it is responding with an unexpected error:
/** *@NApiVersion 2.1 *@NScriptType Restlet */ define( ["N/error"], function (error) { async function _post(context) { throw error.create({ name: "MY_ERROR", message: "This is my error" }) } return { post: _post, }; });
JSON Response:
{ "error": { "code": "UNEXPECTED_ERROR", "message": "An unexpected SuiteScript error has occurred" } }
We would have expect it to respond with this though:
0