NetSuite – Script Execution Time Exceeded (sss_time_limit_exceeded) with Celigo Restlet on Multiple Records

Integrator.io
1

I have a Celigo flow step that has been running unchanged for months without issues. Today, however, I noticed 35 records in error.

The flow step tries to update an Opportunity record for each entry, but I’m getting the following NetSuite error:

{
  "code": "sss_time_limit_exceeded",
  "message": "Script Execution Time Exceeded.",
  "source": "application",
  "statusCode": 400
}

In the NetSuite script execution log, I see:

23/09/2025 14:17:17 SYSTEM Celigo Realtime Import Restlet Runner 
CUSTOMDEPLOY_CELIGO_RT_IMPORT_DEPLOY 9801 Celigo Service Account 
SSS_TIME_LIMIT_EXCEEDED Script Execution Time Exceeded.; ID:

What I’ve tried:

  • Retrying all 35 errors at once → same error occurs again.

  • Retrying a single record → it succeeds without issues.

I don’t know if it the reason is a netsuite script or it has something to do with celigo. But the strange thing is that a single record works and when retrying all records not.

1 Like
2

Hi @nuriensing, this error is usually seen when NetSuite (Restlet) takes more than 5 minutes to process all records in a batch. It could be because of multiple factors like

  • NetSuite is taking longer time to process each record
  • There are multiple sublists in each record which are taking more time to process
  • Temporary issue with NetSuite account

Can you monitor the flow for a few more runs and if the issue persists, try with a lesser batch size. If the issue still persists. please raise a support case and we can have a look at the account closely.

3

Hi,

I’m also experiencing this issue on the payout records starting from November 17th. When I retry the errors, I continue to encounter the same problem. The sublist contains only one record. I have increased the concurrency for the NetSuite connection and even set up a new connection, but the issue still persists. Please share your thoughts.

4

It seems if I retry 30+ at 1 time it doesnt work but if I do like 8 then it works.

5

I’m seeing this issue more and more often when ~20 different records are being pushed into NetSuite (and this is for another Netsuite environment)..

{
  "method": "POST",
  "uri": "https://x.restlets.api.netsuite.com/app/site/hosting/restlet.nl",
  "qs": {
    "script": "customscript_celigo_io_restlet_runner",
    "deploy": "customdeploy_celigo_io_restlet_runner"
  },
  "json": true
}

image
image953×785 96.1 KB

6

I think this might be a potential fix, but please correct me if I’m wrong. It’s possible that too many API requests are being made to NetSuite. One idea to address this could be to set a batch size limit in the import step — for example, setting it to 7. This would group up to 7 records into a single API call, which can help reduce the number of requests and avoid overloading the NetSuite API.

image
image769×445 26.8 KB

7

The default batch size is 100 if nothing is set. The help text is pending an update to this so it's more clear:

Enter the number of records to import to NetSuite at a time. NetSuite's APIs only allows only a certain number of API calls at a time, and each call costs so-called “points” depending on the data, e.g., such as the number of records or the number of lookups configured per record. If too much data is sent at any given time in a single page, then NetSuite might return errors stating that you’'ve run out of points, and hence your flow will fail. You can avoid this by manageing the size of the data sent to NetSuite using the Batch size limit field setting, which. The batch size limit determines the number of records to be sent with each API call to NetSuite. This field setting is useful for certain flow configurations where it’'s not possible to manage the page size for the source data. One example is one-to-many lookups, where each record will result in an exponentially larger number of records being sent to the import. By setting a batch size limit, the results from the lookup will be sent to the import in batches, where the maximum batch size will be per this field's setting’s value, keeping your messages withinand hence, overloading the NetSuite governance. The default system value (when you leave this field setting blank) is 100.

8

Much clearer, thank you, Tyler. I appreciate it.

9

Something else that I find helps this issue is to increase the concurrency of the NetSuite connection if possible. During the holiday season I am seeing this quite a bit especially with Shopify processes.