Questions on integrations/performance (Celigo specifically). I notice that a lot of the flows in Celigo are in the Status of In queue for a long time. (Especially the steps involving interaction with Netsuite). We have purchased extra SuiteCloud licesenses and when I check the concurrency monitor we never come close to hitting the limit. (We have 25 queues and we only get up to 14 or 15 max concurrency). So why are my Celigo flows being stuck in queue for a long time? Is it something to do with the scheduleing of flows within Celigo itself? Or something with how I setup the connections with Netsuite?

Are you using 1 NetSuite connection in Celigo for all of your flows?

Yes

Yeah, it can be all the same user

And that may resolve some of the issues?

Yeah, in Celigo, a connection is also a FIFO queue. All flows using that connection feed the same queue, and the connection’s concurrency is how many pages (batches) can run in parallel. Even if concurrency is 25, NetSuite may take several seconds to respond, especially if workflows or scripts are firing. While those threads are waiting on a response, they stay tied up, which is why you may only see ~15–16 in use. To increase throughput you can reduce page size (so you generate more pages to run in parallel) or split flows across multiple connections (each adds its own queue and up to ~25 threads). If NetSuite rate limits, make sure the Auto-recover rate limit errors setting is enabled so retries happen automatically. Here’s a good reference: https://docs.celigo.com/hc/en-us/articles/360043927292-Fine-tune-integrator-io-for-optimal-performance-and-data-throughput

Thanks @Tyler Lamparter I will try this