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!
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
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
No Limits. Just possibilities.
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.

Kill large numbers of stuck workflows?

edited Dec 2, 2019 3:39PM in SuiteCloud / Customization 3 comments

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!

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!

Leaderboard

Community Whiz

Quarter 4 (Oct-Dec 2025)

This Week's Leaders

This Month's Leaders

All Time Leaders