One for the Celigo fans. When you see this many errors and Celigo's own scripts are timing out, you know it's time to just quit your job and find something new 😄 I estimate it will take at least 6 hours to process the backlog, assuming I can find the route cause.

my guess is that you murdered your item fulfillments with user event scripts / workflows and now it take too long to save records

@battk Maybe, but the scripts running on the IF record haven't changed in over 2 years.

a restlet is doing the importing

Yeah, so that would do the IF .save() then any other scripts that run on that IF would execute once the Celigo restlet terminates right?

thats not how after submit works

I can see four aftersubmit functions deployed against IF, if any one of them takes too long, it will cause the timeout error to be thrown in the restlet then. Nothing has changed in these scripts for a couple of years so not why they're timing out now.

its more likely that the restlet is timing out

message has been deleted

its the user events you want to check

I have fixed over a year of Celigo errors. Talk about fun! Can you retry just a SINGLE fulfillment error and see if that processes first?

any error thrown in the user event is ultimately thrown in the restlet

I'll look through all the scripts and see which one threw the errors. It looks like the issue has resolved itself as fulfilments are flowing through now, I just just have to clear the backlog

You may need to decrease the batch size that you send per request, but we can still send requests in parallel as long as you have more than 1 concurrency set on the NetSuite connection within Celigo. Here are a few good articles on concurrency, governance, and flow optimization. • https://docs.celigo.com/hc/en-us/articles/360034522472-Govern-concurrency-of-NetSuite-connections • https://docs.celigo.com/hc/en-us/articles/360043926372-Configure-connections-to-optimize-throughput-and-governance • https://docs.celigo.com/hc/en-us/articles/360043927292-Fine-tune-integrator-io-for-optimal-performance-and-data-throughput

Batch size is 10, it took a long time to find that optimum number

What is your concurrency setting on the NetSuite connection?

I assume that's this?

That is the max concurrency allowed for that integration setup in NetSuite, but in Celigo you can also specify here

That is set to 1

Then that means Celigo is only sending one page of records at a time across all your flows using that connection

Looks like it requires tokens to change that setting

Sounds good. So I think the combination of decreasing batch size and increasing concurrency would help a lot

Concurrency is now 12 and batch size is 5.