Joy, scheduled script that has been working for years broke on Friday. Logged a bug & it's a known issue with no workarounds. Anyone else had problems with unexpected errors with scheduled scripts?

What line of code did the unexpected error occur on?

It's happening with two completely unrelated scripts, both are erroring when doing a

nlapiSearchRecord()

it may be time to upgrade to nlapiCreateSearch or nlapiLoadSearch

I had an issue with unexpected errors on searches last week, it was with one particular field that was sourced and had Store Value turned off. A defect was issued and it’s resolved now though. If there were no changes to the script I’d recommend creating a support ticket with NetSuite. Before doing so, try to re-create the error in the UI to see if that’s really the issue.

Thank you, but as I said in my original message, I've already logged a bug. U4 defect. It's sporadic, so at least they're processing eventually! 😉

Ooy sporadic bugs are the worst kind. Best of luck!

Cheers 😉

One of our scheduled scripts which has run for 6-7 years has suddenly started erroring, causing major stock issues. You're EU datacenter too aren't you?

Yup

We've also had scheduled mass updates start erroring over the weekend. I get the impression it may have been something in the way of an e-fix before 3am Friday

I had a look & we've had scheduled saved searches fail too

Our scheduled script is erroring with "Scheduled Script deserialization failure, The operation exceeded the time limit and was aborted". It has got a nlapiSearchRecord() operation in the script.

Defect 608675. Thank you!

Just created a case. Our stock and warehouse processes are impacted, which has caused us to oversell quite a lot of stock over the weekend, so I'll be raising it with our account manager if there's not some sense of urgency by tomorrow morning. We're due a tier review on Wednesday which'll be interesting if it's not fixed.

@PNJ, @Dominic B - We're seeing lots of errors for our SuiteApp since Friday.

I opened a case about in on Monday, mentioning @PNJ's case ID. The case was allegedly unrelated (despite our having similar issues) and the error has not occurred since. Not sure at this stage whether they actually fixed/restarted something, or whether it's going to suddenly reappear when our system has a load peak over the weekend.

I gave you a defect ID, I hope that didn't confuse things if they thought it was a case ID 🙂

I did tell them it was a defect ID. You'd hope they'd have the sense to work it out either way, but then again.....

😄

message has been deleted

It's been upgraded to a U3, which is good. I put some pressure on yesterday

I had a call with Netsuite about it yesterday. The latest info I had is that it's "UNEXPECTED_ERROR > Caused by: com.netledger.common.exceptions.NLException: Attempt to execute SQL on a closed connection". Still U3, which is quite unnerving, as a SQL connection going away suggests a significant issue. I'm half expecting everything to suddenly stop working at some point.

It's broken our dunning now

"We would like to let you know that our developers have found a solution for Defect 608675. The fix is being tested and we hope to release it via Hot Push during off-peak hours."

Wow, it's been upgraded to a U2!