When a partner tries to send documents to a partner whose profile is disabled, Trading Networks logs an error message to the activity log, sets the processing status of the document to ABORTED, and sends an email message to the Trading Networksadministrator. If the document was sent using HTTP, Trading Networks also responds to the sender with an HTTP 403 message.

If Trading Networks encounters an error while performing a pre-processing action, it records the information to its activity log and continues to perform the other pre-processing actions. The same is true for processing actions.

If you used the Check for Duplicate Document pre-processing action, Trading Networks might not be able to determine whether a document is unique if:

It could not match the document to a document type.

It previously received the same document but did not save it to the database.

It previously received the same document and saved it to the database, but:

The document type did not indicate to extract the DocumentID, SenderID, and ReceiverID system attributes.

For a flat file, the document gateway service did not place the DocumentID, SenderID, and ReceiverID system attributes in the pipeline.

If you used the Deliver Document By processing action, Trading Networks might require additional information from the receiving partner's profile before it can deliver the document. For example, for immediately delivery methods, Trading Networks must look in the profile for the host name and port for the receiving partner’s system. If Trading Networks cannot determine the required delivery information (for example, because the receiving partner’s profile is disabled), it logs the error to the activity and queues the document for polling.

If a document was sent by one of your partners but Trading Networks cannot determine the sender, Trading Networks considers the sender an unknown partner. If you have a processing rule that processes documents that are sent by the partner, Trading Networks will not select the rule. Trading Networks cannot determine the sender in these cases:

The document type is unknown, so Trading Networks cannot extract any document attributes, including the sender or receiver.

The document type does not indicate to extract the SenderID and ReceiverID system attributes, so Trading Networks cannot determine the document sender or receiver.

The value of the SenderID and ReceiverID system attributes do not match the value of the external ID type of any partner defined in aTrading Networks profile.

In an XML document type, the XQL query cannot find the SenderID and ReceiverID system attributes in the document.