Avoid Concurrency issue by deploying multiple instances of a script.

What Are Concurrency Issues in NetSuite?

In NetSuite, concurrency issues occur when more than one script, user, or process tries to access and modify the same record simultaneously. This is especially common when working with Scheduled or Map/Reduce scripts that are set to handle a high volume of records. Concurrency errors interrupt the workflow, causing frustration and delays, and often require manual intervention or restarting the process.

Understanding Script Deployments in NetSuite

A script deployment in NetSuite allows you to create multiple configurations for running a single script. Each deployment can be set with its own parameters, schedule, and status (active/inactive). For example, by deploying five instances of a scheduled script, you create five separate versions of that script that can run in parallel.

With multiple deployments, NetSuite can execute several instances of the script at the same time, reducing the risk of concurrency errors when processing large datasets.

How Deploying Multiple Instances of a Script Avoids Concurrency Issues

Deploying multiple instances of a scheduled script is beneficial for avoiding concurrency issues because:

1. Parallel Processing: Each deployment acts as an independent instance, allowing multiple records to be processed simultaneously without competing for the same resources.
2. Reduced Queue Times: By having multiple deployments, NetSuite can choose the next available deployment instead of waiting for a single instance to complete its task.
3. Enhanced Error Handling: If one instance encounters an error, it does not impact the other deployments. This reduces the likelihood of a system-wide halt due to a single script failure.

Code Snippet:

 const scheduledScriptTask = task.create({
          taskType: task.TaskType.SCHEDULED_SCRIPT,
          scriptId: 'customscript_', 
          params: {
            custscript_record_type: recType, 
            custscript_record_id: recId 
          }
        });
        const taskId = scheduledScriptTask.submit();