megaphone
Update your Profile with your Support type to get your Support Type badge.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Stay in the know of how NetSuite can help grow your business with our guides, webinars, and events. Subscribe Here
What Topic Should We Cover Next? Your idea could be our next feature—drop your suggestion now!
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. Discover what's next at SuiteConnect Tour 2026.
Try Intelligent Payment Automation – Fee Free For Your First Month For more information, visit this thread.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.

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.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Please note that on Saturday, April 18, 2026, at 8:00 PM Pacific Time, our Case Management System will undergo a scheduled maintenance for approximately 15 minutes. During this time, case creation via SuiteAnswers will be unavailable and inbound calls will be routed to Customer Service.

Why would nlapiInitiateWorkflow() throw "RCRD_HAS_BEEN_CHANGED" exception?

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

Howdy everyone,

I have a scheduled script that is processing a few hundred sales orders daily. It *mostly* works fine, but there are 10-15 events a day where the call to nlapiInitiateWorkflow() results in NetSuite throwing a

RCRD_HAS_BEEN_CHANGED

exception. I've checked and verified there are no updates in my code, it's a dead simple script, 71 lines most of which are infrastructure and plumbing.

Considering we can't pass an nlobjRecord reference to the nlapiInitiateWorkflow() method I don't see how I can be the cause of a concurrency fault. I'm tempting to put a simple retry mechanism in place but I'd rather understand WHY this is happening first.

Steve Klett | Senior Developer
NetValue Technology

image-8cb77df5036e1-7e7f.png

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 2 (Apr-Jun 2026)

This Week's Leaders

This Month's Leaders

All Time Leaders