When you view the list of errors encountered in a flow, each open and resolved error is labeled according to its type, or “classification.” Errors are categorized according to their properties, such as the code, message, and source fields.
The Classification column helps you quickly recognize and filter errors, even when the escaped JSON or third-party app error messages are difficult to read.
Then, in the detailed view per error, the classification appears above the trace key.
Errors are automatically placed into one of the following seven read-only classifications; the value is blank if none of them applies. Contact support if the classification appears to be incorrect.
Classifications
Value
| Sample error messages | Typical cause |
| Invalid phone value: remove dashes | The value provided causes a specific problem |
| Order status == cancelled in target system. Target system rejects all updates | An unexpected value prevents any changes to the record in the destination system |
| Transaction was declined by processor. Issuer Declined | |
| Cannot change status field | The destination system prevents all changes to a specific field of the record, and any new value sent for this field is rejected |
Missing
| Sample error messages | Typical cause |
| The field last name was not found in the source data | A required resource or field – for either the source or destination system – is empty or missing |
| A mapping error occurred. Could not find a match for \"[[\"nameinternal\", \"is\",\"ACXB17339D\"],\"AND\",[\"isinactive\",\"is\",\"F\"]]\" for the record type \"item\". |
|
| We cannot recognize your child SKU[ABCS-AE9…] | |
| Failed to add Amazon Order# 112-3043730-4965007. A mapping error occurred. Could not find a match for \"[[\"nameinternal\",\"is\",\"sku-m-sl-029\"],\"AND\",[\"isinactive\",\"is\",\"false\"]]\" for the record type \"item\"." | |
| We could not access the media at URL http://12345_example.jpg | A resource cannot be found at the path provided |
Connection
| Sample error messages | Typical cause |
| You do not have permissions to edit this transaction. | The user does not have permission to access or edit the record |
| Failed to update price for item with SKU# KRYP-18STALSH8 due to following error from eBay : Validation of the authentication token in API request failed. | The user supplied an incorrect username/password or an invalid or expired access token |
Intermittent
| Sample error messages | Typical cause |
| Connection timed out | The operation may work when retried, meaning that the error is not always repeatable and the endpoint successfully recovers without any changes to the request in integrator.io |
| Failed to export fulfillment for Walmart Order# 3796505942910 : System encountered some internal error, Internal server error for3796505942910 Unknown error occurred on the server | |
| Connection to remote server is closed.[socket hang up] | |
|
|
|
|
|
Governance
| Sample error messages | Typical cause |
| next call will cost 10 points while only -12 avail. | An API request exceeds the number allowed in a period of time or exceeds the customer’s API quota |
| {\"status\":\"error\",\"message\":\"You have reached your secondly limit.\", \"errorType\":\"RATE_LIMIT\", \"correlationId\":\"eaa828b5-c14e-4be5-acd1-fa4e985fcaae\",\"policyName\":\"SECONDLY\", \"groupName\":\"publicapi:hapikey-api-calls-secondly:2627175\",\"requestId\":\"0e499ad7-1e1e-4c0a-b1ed-4a0f83252488\"} |
|
| Failed to fetch order items for Order# 114-8662394-0783433 due to API throttling. Please retry again. | A request or operation took too long – try to make the request smaller or split the operation |
Parse
| Sample error messages | Typical cause |
| Hook file error - SyntaxError: 'try' without 'catch' or 'finally' | The integrator.io script engine encounters tokens or token order that does not conform to the expected syntax of the input language |
| An invalid JSON is sent in the response.body, error: Unexpected string in JSON at position 1831. | |
| SyntaxError: Unexpected end of input | |
| Unexpected token } in JSON at position 191, please ensure that you have wrapped all JSON property names in quotes. | |
| An invalid JSON is sent in the response.body, error: Unexpected token ' in JSON at position 1. | |
| Failed to add Shopify Order #1700510007371. Could not compile handle bar \"{{#compare source_name \"==\" \"pos\") }}13143{{else}}23863{{/compare}}\" because \"Parse error on line 1:\n...urce_name \"==\" \"pos\") }}13143{{else}}238\n-----------------------^\nExpecting 'CLOSE', 'OPEN_SEXPR', 'ID', 'OPEN_BLOCK_PARAMS', 'STRING', 'NUMBER', 'BOOLEAN', 'UNDEFINED', 'NULL', 'DATA', got 'CLOSE_SEXPR'\" .Please correct and retry |
Duplicate
| Sample error messages | Typical cause |
| Failed to add Shopify Order #1686494216262. Order with Order Id# 1686494216262 has already been imported into NetSuite with NS Id# 5283408 | The destination system has an existing record or the lookup system finds more than one matching result |
| OpenAir Project ID: more than one record found for external id field: [a0O6A000000FTTSUA4, a0O6A000000FTobUAG] | |
| duplicate value found: NetSuite_External_ID__c duplicates value on record with id: a0W4N000009jsah | |
| {\"description\":\"Email: carmen@toreador.io is already being used by another user\",\"error\":\"DuplicateValue\"} | |
| A contact record with this name already exists. Every contact record must have a unique name.\nThis error is for the Zendesk records with internal ids - 388639824392 | |
| {\"error\":\"RecordInvalid\", \"description\":\"Record validation errors\",\"details\":{\"name\":[{\"description\":\"Name: NSW Department of Justice has already been taken\",\"error\":\"DuplicateValue\"}]}} This error is for the NetSuite records with internal ids - 3249 |
|
| A duplicate value was specified for field 'Case_Sub_Category__c' in object 'Case', duplicate value 'signature_management' prior value 'feature_request' | A duplicate value is given for a field |
Blank value
The error cannot be classified with high confidence, despite the millions of integration and API errors and artificial intelligence at Celigo’s disposal. However, such occurrences are regularly reviewed for additional classification.
Comments
0 comments
Please sign in to leave a comment.