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.
Kill large numbers of stuck workflows?
Hi,
I have an unfortunate situation whereby an old version of a workflow has become 'stuck' because it entered a state with no matching transition out of it.
In the meantime, someone else added in some 800 records for testing, all of which have now become 'stuck'. Is there any way to batch cancel such workflows, as unfortunately it stops new instances of the workflow from running?
As a workaround to the running issue, I suppose I could duplicate and rename the workflow so that NS sees it as a different workflow, which would then execute. However, it's still not great having old workflows stuck on a record (even though the end users won't ever see them, only admins get to see the active workflow/history tabs) and I do not relish stopping ~800 workflows by hand!