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!
Stay in the Know
Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe
Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe
Please note that on Friday, March 20, 2026, at 8:00 PM Pacific time, our Case Management System will undergo a scheduled maintenance for approximately 4 hours. During this time, case creation via SuiteAnswers will be unavailable and inbound calls will be routed to Customer Service.
How do I call a scheduled script again in 2.0 where it was left out previously?
I'm encountering challenges with NetSuite Governance Unit limits in my scheduled script. To address this, my current strategy involves processing 50 records during each script execution. After processing a set of 50 records, I trigger the scheduled script again with an incremented range, such as 51 to 100, for the subsequent execution. This iterative process continues until all records are processed. I'm seeking suggestions on how to enhance this approach for better efficiency and to overcome NetSuite's governance limits. How can I optimize this solution, and are there any best practices I should consider scheduled script 2.0?
Tagged:
0