The Script Debugger in NetSuite enforces specific metering and permission restrictions across all SuiteScript versions (1.0, 2.0, and 2.1) to ensure efficient debugging and system integrity. Here are the key points to understand:
- Debugging Restrictions: Single Script Debugging: Users are limited to debugging only one script at a time. Attempts to debug multiple scripts concurrently, such as opening multiple browser windows, will result in both windows displaying the same script/debugging session.
- User-Specific Script Debugging: Users can debug only their own scripts within their current login session.
- Usage Limit: There is a usage limit of 1000 units on all scripts being debugged. This limitation is crucial to note, especially for script types like scheduled scripts, which are allowed 10,000 units when running in NetSuite.
- Email Error Notifications: Email error notifications are disabled for scripts being debugged.
- Execution Log Display: For SuiteScript 1.0 and SuiteScript 2.0 scripts, execution log details are displayed on the “Execution Log” subtab in the Debugger instead of the execution log on the Script Deployment page. For SuiteScript 2.1 scripts, execution log details are shown on the “Console” tab of the Chrome DevTools debugging window.
Idle Timeouts:
- SuiteScript 1.0 and 2.0: There is a two-minute time limit on scripts sitting idle in the debugger. After two minutes of inactivity, users will receive an error message prompting them to start a new debugging session.
- SuiteScript 2.1: Idle timeouts work differently in the 2.1 Script Debugger. There are two scenarios: If there has been no user action within the debugger for five minutes, Chrome DevTools will disconnect, requiring users to start a new debug session. There’s also an overall time limit for a debugger session, set by the IDLE_SESSION_TIMEOUT_IN_MINUTES general preference. This preference also sets the timeout for a NetSuite user session.
Error Handling and Recovery:
If any of the timeout errors occur, users can return to the Script Debugger page and stop debugging. They can then reload the script and start a new debugging session.