Any Celigo folks here encounter an intermittent er...
# integrations
a
Any Celigo folks here encounter an intermittent error when updating a record but is fine when creating a record on Add/Update
t
Not that we've seen. Do you have "auto recovery of errors" turned on?
a
No it is not enabled
t
Any reason to not have it enabled?
It would auto retry those intermittent errors for you
a
It's just how I inherited the environment
t
All good. I would enable it and then you'll see errors that are classified as intermittent will get auto retried
If the flow is old enough, it wouldn't have it enabled because I don't think we enabled this functionality for flows made prior to this feature. Though this feature was made a couple years ago.
a
Are intermittent errors just a thing you live with? Are there any methods to mitigate them from occurring?
t
What's the exact error you're getting from NetSuite? Can you screenshot it?
As for living with, intermittent errors are common and not under our control so there often isn't much you can do which is why we built out this auto retry functionality
a
Nothing specific
Copy code
Failed to save record because null Possible reasons include > Something went wrong on NetSuite side. > You might have specified an invalid field value for a field. > You may have submitted an invalid record. Please consult NetSuite Support with NLAPI calls obtained from NetSuite Connection Debugger
t
And if you retry it always goes through?
Also, how many of these are we talking? Like how many records fail with this out of total success?
a
It looks like retries resolve it, I would say about 10% of executions
return an intermittent error
t
Weird. What record are you adding/updating?
Any major scripts or workflows on those?
a
sales orders sfdc to netsuite
no its just a listener to import
t
I mean in NetSuite on the sales order record. Are there lots of workflows or scripts running on that record beforeSubmit, afterSubmit etc?
a
4 scripts 1 workflow
only 1 UE is actually a customization others are from bundles
one being from celigo
other 2 are the drag n drop
g
We had the same issue with our Celigo flow from SF to NS. It took us a while to resolve this issue. We resolved the problem by removing the currency mapping from Celigo.
a
Hm I did suspect a mapping issue, however we don't have currency specifically I don't think
Thanks for the insight
g
Check each of your mapping. Disable them one at a time. Thats how we discovered our issue.
a
Did you encounter an intermittent error consistently per retry data?