Celigo Error:
“Failed to add Amazon Order# 114-0556364-1777836. A mapping error occurred. Could not find a match for \”[[\”nameinternal\”,\”is\”,\”New_Salad_Spinner\”],\”AND\”,[\”isinactive\”,\”is\”,\”false\”]]\” for the record type \”item\”.”
Solution:
The item record for New_Salad_Spinner in Netsuite is either inactive or non-existent. It needs to be created and activated. Then we need to click “retry” on the error in Celigo.
Celigo Error:
“Failed to add Amazon Order# 402-5142824-5305943. Failed to save record because The field state contained more than the maximum number ( 30 ) of characters allowed.”
Solution:
Go to the error in Celigo and click the ‘Edit Retry Data’ button. In the ‘StateOrRegion’ field, There will often be duplicate text, or text that should be in ‘AddressLine1’ (for example “Flat B004, Ground Floor”), so either remove the duplicate text or cut and paste the necessary text into ‘AddressLine 1’
We do not need the field state on order flows because finance does not process customer information. So we hardcoded the value of the state fields to the country of the order.
Celigo Error:
“Failed to create, update/transform record because You have attempted an invalid sublist or line item operation. You are either trying to access a field on a non-existent line or you are trying to add or remove lines from a static sublist.
Solution:
This is because of more than 10,00 open Invoices are there for the customer used in the order. So need to create new customer and assign some Invoices to the new Customer using CSV Import.
Celigo Error:
“Credit Memo not created. Invoice is not paid sufficiently to process refund. Invoice status: open, Amount Paid in NetSuite: 0, Amazon Refundable Amount: 21.99. Settlement details: Settlement Id# 14900171171, Amazon AFN Order# 113-7116800-2266606.”
Solution:
This is is because of the absence of payment record corresponding to an Invoice.
No Action required. These errors get picked up on the next execution of the payment flow and then we can retry the data.
Celigo Error:
“Failed to add Amazon Order# 112-9611501-7189849. Failed to save record because Inventory items must have a positive amount.”
Solution:
Change the ‘NetSuite discount item to track Amazon item discounts at line-level (recommended)‘ setting on the flow to ‘Amazon Discount US‘ . Go to:
Amazon – Netsuite → ENTITY → Order (FBA) → Settings → Orders → NetSuite discount item to track Amazon item discounts at line-level (recommended)‘ setting on the flow to ‘Amazon Discount US (Changed from ‘Amazon Discount’ to ‘Amazon Discount US’
Celigo Error:
“Extension returned statusCode 504. Expected 200. Response body =”
Solution:
Just retry the data. 504 is an internal error code, meaning the issue was with Celigo’s server, nothing we can do about it other than to retry when the issue is resovled.
Note: SOME of these errors seem to retry/resolve automatically the next time the flow runs (if it is a Delta flow at least, which our FBA flows are), but other order don’t retry automatically, even if they are for the same flow and same error batch as some orders that did auto-resolve. To be safe, always retry the data.
Celigo Error:
“Script Execution Time Exceeded.”
Solution:
No action required. These errors will be picked up on the next time the flow runs. At least, this is the case for Delta flows (which is what our order/FBA flows are).
Celigo Error:
“Extension returned statusCode 504. Expected 200. Response body =”
Solution:
Retry the data. These errors sometimes resolve themselves the next time the flow runs, but I have come across multiple occurrences where this is not the case, so always retry the errors just to make sure they are resolved
Celigo Error:
“!!Something went wrong, invalid options passed to the hook.”
Solution:
No Action required. These errors get picked up on the next execution of the flow
Celigo Error:
“Failed to Add/Update customer for Amazon Order# 113-9612418-2504215. null”
Solution:
No Action required. These errors get picked up on the next execution of the flow
Celigo Error:
“Failed to add Amazon Order# 113-6742260-6621839. Failed to save record because This record already exists”
Solution:
If this error occurs on the import sales order flow, then we can just mark them as resolved because the order already exists.
“Failed to Add/Update customer for Amazon Order# 112-6955366-4689018. Failed to save record because Record has been changed”
Solution:
Retry the data.
Celigo Error:
“Failed to save record because null Possible reasons include\n> Something went wrong on NetSuite side.\n> You might have specified an invalid field value for a field.\n> You may have submitted an invalid record.\nPlease consult NetSuite Support with NLAPI calls obtained from NetSuite Connection Debugger. Settlement details: Settlement Id# 14900171171, Amazon AFN Order# 112-7679771-4580216.”
Solution:
This error occurred on the ‘create payment’ node of the flow. The solution was just to retry the data – this created the payment record in Netsuite.
Celigo Error:
“Failed to add Amazon Order# 114-6975677-6764242. Unable to load timezone file: Celigo/Resources/Celigo.lib.timezone.OlsonTimeZoneData.js | Name: UNEXPECTED_ERROR\nMessage: null\nStackTrace:\n\tat Celigo_Basis.closure.js:972\n\tat Celigo_Basis.closure.js:935\n\tat Celigo_Basis.closure.js:935\n\tat Celigo_Basis.closure.js:996\n\tat Celigo_Basis.closure.js:1052\n\tat Celigo_Basis.closure.js:1589 (b)\n\tat Celigo_Basis.closure.js:1597\n\tat Celigo_Basis.closure.js:1591 (e)\n\tat Celigo_Basis.clo…”
Solution:
No Action required. These errors resolve themselves the next time the flow executes
Celigo Error:
“Failed to Add/Update customer for Amazon Order# 113-4112117-8371425. Failed to create, update/transform record because An unexpected SuiteScript error has occurred Possible reasons include\n> Something went wrong on NetSuite side.\n> You might have specified an invalid field value for a field.\n> You may have submitted an invalid record.\nPlease consult NetSuite Support with NLAPI calls obtained from NetSuite Connection Debugger.”
Solution:
No Action required. I am not sure why we get these errors because the customer is added to the order record, and retrying the data does nothing to update the Sales Order in Netsuite.
Celigo Error:
“Failed to fetch order items for Order# 113-2759262-6945849 due to API throttling. Please retry again.”
Solution:
No action required, these errors resolve themselves the next time the flow executes for Delta flows
“Failed to add Amazon Order# 112-1703511-7804260. Failed to create, update/transform record because Your session has timed out. Please re-enter your information and try again.”
Solution:
No action required, these errors resolve themselves the next time the flow executes for Delta flows
Celigo Error:
“Failed to add Amazon Order# 111-9737581-8273019. Failed to save record because null Possible reasons include\n> Something went wrong on NetSuite side.\n> You might have specified an invalid field value for a field.\n> You may have submitted an invalid record.\nPlease consult NetSuite Support with NLAPI calls obtained from NetSuite Connection Debugger.”
Solution:
Retry the data. Sometimes these errors resolve themselves the next time the flow runs itself, but sometimes they don’t and I am not sure why.
Celigo Error:
“Failed to Add/Update customer for Amazon Order# 112-1899968-2550658. Failed to save record because Please enter value(s) for: Company Name”
Solution:
retrying doesn’t always work (example 113-7553088-6301824 (AMZ-US-9 GLB, that errored on 18th Nov 2021). Wait a few days to see if this resolves itself….
No action required. I am not sure why we get these errors. On the example above, the customer was added to the order on 23rd Oct 2021, but we got this error on 12th Nov 2021. And there was no information in the System Notes of the order to suggest the customer had ever been changed, and the CUSTOMER field is mandatory, so it couldn’t have been ignored.
Celigo Error:
“Failed to add Amazon Order# 112-2693295-1663418. Failed to save record because invalid item reference key 4892 for subsidiary 9.”
Solution:
The item is not set up for subsidiary 9. Set the item to the top-level/parent subsidiary and tick ‘Include children’
Celigo Error:
“Failed to add Amazon Order# 112-1580401-5599457. Failed to save record because Invalid subsidiary reference key 53 for entity 1752.”
Solution:
The Branded flows use a default customer for each subsidiary so they don’t have to import unnecessary customer details. I had copied the Rohego flow when setting up Buckthorn (BKT), so this error was because the default customer was 1752 which was the Rohego default customer. So I made a BKT default customer (id = 7477) and assigned it in:
Amazon – Netsuite → AMZ-US-2 BKT → Order (FBA) → Settings → Customers → Allocate FBA orders to below NetSuite customer(s)