Slow performance Netsuite EU

Integrator.io
1

Hi everyone, I’m running into a strange performance issue with a NetSuite lookup in Celigo + NetSuite (Sandbox) and I’m hoping someone can help me understand what might be causing it.

I only have one NetSuite connection in this environment, with full concurrency enabled, and at the moment I’m only running one flow related to this issue. The Celigo dashboard is basically empty (no queue, no backlog, no obvious congestion), except for this one active flow run.

The problem is that the lookup steps in the flow are extremely inconsistent: sometimes they run almost instantly, but other times they take a very long time to respond, even though nothing has changed in the flow configuration.

What makes it even more confusing is that the NetSuite saved search is tiny (it currently returns only 2 rows) and the dataset is minimal, so I wouldn’t expect performance problems from the NetSuite side. Also, when I run the lookup using the mock response, it always returns instantly, and the steps that follow are very minimal as well.

I also disabled Auto Resolve, but I’m still seeing cases where each step takes around 1 minute, even though the data volume is extremely small..

Has anyone seen NetSuite lookups behave like this in Celigo, where the same lookup can be fast one moment and slow the next, even when the environment looks healthy? I’m trying to figure out whether this could be related to NetSuite performance or something else?

image
image1728×402 58.4 KB

2

I had a similar issue when trying to look for customer addresses (the issue was there in both sandbox and production). Sometimes it works well and the other times it gets really slow and takes minutes to look for customer addresses.

The way I solved was using a parameter to look for addresses of a customer that makes sense to the NetSuite. Previously I used email address of the customer but as I was able to grab the internal ID of the customer in a previous step, I started using internal Id to get addresses of the customer.

So basically, if you can use internal ID (whether it is a customer record or a main table record), then lookups work much faster when compared using another parameter.