Hello, I don't know scripting, but I have a question. We have an integration with a third part app that creates/updates items and BOM's in Netsuite. This integration is executed via schedule scripts within Netsuite and it run every hour; however, when we have a lot of data or large BOM, it takes a while and seems that only process few records and picks up and continues next time it runs. • Is there any such thing as time out? • Is there a time limit that a schedule script can be running before Netsuite stops it? Thank you

Is it a Scheduled Script, or a Map/Reduce script that's running on a schedule? It might be running into a governance issue - each Netsuite script has a finite number of governance units that different actions consume as the script processes data.

Limits documented here: https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N3351480.html#Script-Type-Usage-Unit-Limits

@Clay Roper Without really knowing the difference, I see the script running under the "Scheduled Script Status" queue and not under "Map/Reduce Script Status". Thanks @CD Thanks a lot for the link. I will look at it. Honestly, the integration job was not having issues before; however, new scripts where introduced (with multiple deployments) when Items are updated, so I believe those executions are now creating this problem.

As others mentioned their is both, scheduled scripts have a governance limit of 10,000 and time limit of 60 minutes. The other common issue i see is when their are multiple scripts running concurrently is a RECORD HAS CHANGED error. That could be what is happening as well, specially for larger transactions that take a while to save. I would start off on the Script Execution Log page and then filter by the different log levels to help narrow it down.

Thank you all for the information.