Error code: SSS_TIME_LIMIT_EXCEEDED
Platform: NetSuite (via Celigo integrator.io)
Affected steps: Export, lookup, import
What you see in integrator.io
When this issue occurs, the error record displays the following details:
-
Message:
Script Execution Time Exceeded. -
Source:
NetSuite -
Code:
sss_time_limit_exceeded -
Classification:
Too large
The SSS_TIME_LIMIT_EXCEEDED error, displayed in integrator.io as Script Execution Time Exceeded, occurs when NetSuite cannot complete an operation within its 5-minute server-side scripting time limit.
For flows that process data in pages, this limit applies to all operations performed within a single page. For example, if a flow has a default page size of 20 and an import step that creates NetSuite sales orders, NetSuite must be able to create and save all 20 sales orders within 5 minutes. If it cannot, the error SSS_TIME_LIMIT_EXCEEDED is thrown.
Cause: The saved search associated with the export or lookup step is taking too long to run. This delay is common in searches with a large number of transactions.
Fix: Add stricter search criteria to the saved search to reduce its run time. For best results, place the most restrictive criteria at the top of the saved search criteria list. Since NetSuite evaluates criteria in order, leading with the narrowest filters reduces the result set early and speeds up the overall search.
If the error occurs on a NetSuite import, work through the following troubleshooting steps in order. Proceed to each step only if the issue persists.
Review the import field mappings and reduce or eliminate dynamic lookups where possible. A lookup cache is a good alternative.
If a dynamic lookup cannot be replaced, add specific and targeted search filters to each one. Narrowing the search scope reduces the time NetSuite spends resolving each lookup during the import.
If the import step is configured with a deduplication search (configured under How should we handle existing records?), make sure that the search uses strict, targeted criteria. A deduplication search that scans too many records will add significant time to each page of the import.
Review any SuiteScript hooks configured on the import. Also check for NetSuite workflows, user-event scripts, or other automation triggered when NetSuite creates or updates the affected record.
Use the timestamp shown in the integrator.io error record to review the corresponding NetSuite script execution logs. Optimize or deactivate any custom automation that consumes excessive execution time.
If the logs identify a Celigo-managed script, SuiteApp, or RESTlet, do not modify or deactivate it. Continue with the remaining troubleshooting steps and contact Celigo Support if the error persists.
If you’ve reached this point and the import is still timing out, reduce the Page size or Batch size setting on the NetSuite export. For example, if the flow is processing 50 records per page and NetSuite cannot save 50 sales orders within 5 minutes, try reducing the page size. Fewer records per page mean less total work per operation, giving NetSuite more time to complete each batch.
If the import continues to hit SSS_TIME_LIMIT_EXCEEDED after completing all of the steps above, the root cause may be a broader performance issue within NetSuite itself — such as SuiteScripts or workflows concurrently running on the affected record type.
To investigate, open your NetSuite account:
- Navigate to Record Pages Monitor.
- Set the time range to Last 30 Days.
- Sort results by Highest Response Time.
- Click Refresh (at the top right) to apply the sort changes.
- Review the Save time for the record type used in your flow.
If the times are consistently high, ask your NetSuite administrator to review any SuiteScripts or Workflows configured to run on that record type (from the Script Records list).
Contact Celigo Support
If the error persists after you complete the troubleshooting steps, contact Celigo Support and provide:
- The error ID and timestamp
- The integration, flow, and step names
- The error request and response
- Relevant NetSuite script execution logs
- The installed versions of the Integration App and related Celigo SuiteApp, if applicable
If a Celigo-managed script appears to be consuming the execution time, do not modify the script. Celigo Support can review the execution details and determine whether an Integration App or SuiteApp update or another managed resolution is required.
| Step type | Common cause | Primary fix |
|---|---|---|
| Export or lookup | Saved search is too slow | Add stricter search criteria; move narrowest filters to the top |
| Import | Dynamic lookups, SuiteScript hooks, or large pages | Replace dynamic lookups with lookup cache; reduce page size |
| Import (error persists) | NetSuite-side performance issues | Use Record Pages Monitor; consult NetSuite admin |
| Integration App import | NetSuite automation or a Celigo-managed script consumes the execution window | Review NetSuite execution logs; do not modify managed scripts; contact Celigo Support |