Intro to asynchronous messages

This is the first step in the validation process as a file is received by TraceLink. This error is most often caused when required data is either missing or incorrect. This failure indicates that the file was poorly structured (e.g. data elements are in an incorrect order) or contained other errors that prevented TraceLink from integrating and processing the file. These instances trigger schema validation errors. In short, this error indicates that an inbound message has failed data translation. Map In Failed and Map Out Failed may also point to system errors in the map call.

An inbound message is designed to convert an external party’s data format to Tracelink's format. The external party sends data to Tracelink for data transformation, therefore Tracelink is the recipient of the data.

This is considered the second step in the validation process and generally where all of the business logic is found. This error indicates a failure at any point in a transformation document life cycle (e.g. transmission failure or back end code failure).

This step is when TraceLink maps the outbound data, converting it into the receiving party's preferred format. Sometimes the rules can vary based on the file format. This error indicates an outbound message has failed at some point in this data conversion process. Map In Failed and Map Out Failed can also point to system errors in the map call.

A blocked error indicates a system blockage or processing failure.

This error indicates a processing error or message data translation failure. This error type requires investigation to determine the root of failure. Often, this error occurs when the system believes it is receiving a duplicate file.

Class 1 errors are mapping validation errors. These errors fall under the "Map In" error type. This is where the data structure of the message is validated (e.g. where data type information or an element's required or optional requirement is validated. Map In errors are returned if there is an issue with this first validation step. For example, if a required field is omitted, a class 1 error results.

Class 2 errors are data translation errors which can be found in the "Processing Failed" category of errors. A Processing Failed error type indicates that the map failed to translate to TraceLink's internal format and therefore cannot hit the back end API. Think of this second step as an "integrity check" against the submitted data. For example, if a serial number is submitted but is assigned to an incorrect product code, an error results. Another example is if a certain event (such as Commission) is submitted, but the serial number included in that event is unrecognized, an error results. The following are some class 2 error examples:

Class 3 errors occur when data translation to a third party (Trade Partner) fails due to an internal server error. Class 3 errors are rare, though they may still occur due to missing or incorrect information in the Master Data. The troubleshooting recommendation for Class 3 errors is to first check Master Data, make appropriate edits, and then resubmit the designated file. If Master Data is correctly configured, contact Support for further assistance.