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.
Have questions or experiences to share? Post your Release 2026.1 questions and join discussions in the Release 2026.1 category.
Intelligent Payment Automation, powered by BILL (formerly 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.
stacking up scheduled scripts
I need to schedule a script many times. I assumed that if I scheduled it 10 times they would just stack up and be processed in the order they were scheduled.
It seems that if a deployment has a scheduled status of "IN PROGRESS" and you try to schedule that deployment again it will fail.
I really hope that I don't need to create a "pool of deployments"!
So to summarize: I schedule script 'abc' deployment '123'
I schedule it again while the first schedule is running and this seems to result in the second scheduled event being ignored.
What is the best practice in this scenario? It's possible that with each user of my desktop application I could schedule up 20 deployments per user, per operation. These are short running scripts so I'm not concerned about the volume.
Steve Klett | Senior Developer
NetValue Technology
