Any other users experiencing abnormally long wait times in their Map/Reduce scripts? Our scripts that were normally taking approximately one minute to complete, are now taking 20+ minutes @Nick @rickthewilliams Example:

Not so far.

@Elizabeth Bunker Does your environment have a number of active scripts during that time of day? I wonder if this was deprioritized on the processor and/or yielded for some reason.

Yes, and that is our typical scenario. Sometimes it does take upwards of five minutes if many are queued. But we have never seen this much of a delay before. And we are unsure of why we are seeing that delay in between the reduce and summarize stages of the scripts, noted in the highlighted portion of the screenshot.

Yes, it started after our 2024.1 pre-patch. 5 minutes has turned into 40. The big overnight one wants to take hours. We've moved to manual processing (the script auto-fulfills overnight orders)

We have escalated this and have a support case created. But no updates yet. This started either last week or the week before for us as well.

curious if anyone sees a perf hit on Scheduled Scripts, or is this just a M/R problem?

NetSuite classified this for us as a U3 defect. They confirmed that processors were available in our accounts but our scripts were not started. Not sure if the e-fix would be for just our account? But there is hope for those with this issue if they make a business case for it....if their e-fix works.

They didn't. I got a tip yesterday from a contact there who asked around for me, and it appears to be (to me) an undocumented change in concurrency limits. He suggested I try setting limits to NULL and letting the system run with it. I think that they may have changed it from min to only logic. But I have no proof of that.

Did setting yours to null improve performance / did you see a change?

It did. I'm down to 90 mins on our overnight (from 6 hours) and back to 5 minutes on the hourly (from 35)