If you inactivate the user who is owner of a set of scheduled scripts or map / reduce scripts, and those script records are locked due to them coming from a bundle that given user installed in the past, what is the best way to proceed? The goal is to make sure that the scripts still run as they were running originally. I have tried updating the bundle so the owner would be update, but as they are managed bundle, this is not possible. I see there is no owner in the deployment, which is editable. If I were to create a new deployment of that script with the inactivate owner, will it run? Documentation for reference: NetSuite Applications Suite - Inactivating Users https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1525773325.html Effects of Removing Access to the Owner of Report, Saved Search and Custom Record https://suiteanswers.custhelp.com/app/answers/detail/a_id/28344/loc/en_US Owner of the Installed Bundle Cannot Be Changed https://suiteanswers.custhelp.com/app/answers/detail/a_id/74837/loc/en_US

I'm not sure there's any impact to this whatsoever, its very common for some implementation consultant to have installed various bundles before go-live, and 90% of them are no longer around 2+ years later. The only thing you have to be aware of is updating the error messaging to send to someone other than script owner. An employee group made up of current admins is the best way I've seen to address this, and you set all scripts to send errors to that employee group. Then you just need to keep the group updated as you hire/lose admins 🙂

That is what makes it confusing, because I thing it should a fairly common situation. According to this link NetSuite Applications Suite - Inactivating Users - https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1525773325.html They say the following: "Any jobs, for example, reports or scripts, that were scheduled by a user who is now inactive are not run. The jobs are still available, but the schedule is deleted." So I feel that this basically implies that schedule scripts whose owner cannot be changed due to belonging to a lock bundle means they will not run anymore. I am not worried about not receiving the notifications if an error happens, but more that those scheduled scripts do not run. Specially as they belong to lock bundles sometimes is difficult to assest what they exactly do and what is the importance of them not running. Anyone has experience on this situation?

I'm not sure what to tell you, this is a non-issue, that doc is simply wrong with regard to scripts. Curiously the quoted text looks a lot like the 2nd bullet point about reports, which doesn't mention scripts at all.

• If the user set up schedules to run reports, the reports are not run. The schedule definition is still available, but the task stops running because one part of the schedule was deleted.

You are totally right, I have done a test - inactivating the user and checking whether those scripts still run as expected and indeed is the case. So indeed the documentation is misleading. Thank you very much!