> ## Documentation Index > Fetch the complete documentation index at: https://docs.transitive.app/llms.txt > Use this file to discover all available pages before exploring further. # Event codes > The event statuses and the messages on the Events page. Use this reference to read the **Events** page. Each event has a status. An event that did not become a document also has a message. To learn how the **Events** page works, refer to [Check what CargoWise sent](/cargowise/events). ## Event statuses | Status | What it means | | - | - | | **OK** | Transitive used the message. The document is new or updated. No action is necessary. | | **Processing** | Transitive received the message and has not finished. The status changes by itself. | | **Duplicate** | Transitive already has this exact message. No action is necessary. | | **Stale** | Transitive did not use the message. It is older than the data that Transitive has. No action is necessary. | | **Quarantined** | Transitive kept the message and created no document. Read the message of the event to find the reason. | | **Failed** | Transitive could not receive the message. Send the document from CargoWise again. If it fails again, contact Transitive. | ## Messages The **Message** column of an event shows one of these messages. | Code | Message | | - | - | | [`invalid_body`](#invalid_body) | Not readable as XML | | [`invalid_content_type`](#invalid_content_type) | Wrong content type | | [`payload_too_large`](#payload_too_large) | Message too large | | [`cargowise_fault`](#cargowise_fault) | CargoWise reported a fault | | [`non_accounting_event`](#non_accounting_event) | CargoWise event, not a document | | [`unsupported_message`](#unsupported_message) | Message type not stamped | | [`organization_identity_missing`](#organization_identity_missing) | CargoWise enterprise not named | | [`organization_mismatch`](#organization_mismatch) | Company identity didn't match | | [`company_unidentified`](#company_unidentified) | Company couldn't be identified | | [`company_conflict`](#company_conflict) | More than one company matches | | [`company_evidence_required`](#company_evidence_required) | Company not named | | [`company_credential_mismatch`](#company_credential_mismatch) | Another company's document | | [`company_unconfigured`](#company_unconfigured) | Company isn't configured | | [`document_number_missing`](#document_number_missing) | Document has no number | | [`message_structure_invalid`](#message_structure_invalid) | Message structure not understood | | [`document_unmappable`](#document_unmappable) | Document could not be read | | [`ambiguous_fiscal_receipt_batch`](#ambiguous_fiscal_receipt_batch) | Several receipts in one message | ## `invalid_body` > **Not readable as XML** The message is empty or is not valid XML, so nothing could be read from it and no document was created. The stored payload shows what arrived. * **What to do:** Make sure that CargoWise sends valid XML. Then send the document from CargoWise again. ## `invalid_content_type` > **Wrong content type** The message was not sent as application/xml or text/xml, so it was not read and no document was created. * **What to do:** Set the content type of the CargoWise outbound integration to `application/xml`. Then send the document again. ## `payload_too_large` > **Message too large** The message is larger than Transitive accepts, so it was not read and no document was created. * **What to do:** Send a smaller message. The limit is 25 MB. Then send the document from CargoWise again. ## `cargowise_fault` > **CargoWise reported a fault** The message is an error report from CargoWise, not a document. The stored payload has CargoWise's own text. * **What to do:** Open the event and read the text from CargoWise. Correct the cause in CargoWise. ## `non_accounting_event` > **CargoWise event, not a document** The message is a CargoWise event, not an invoice, credit note or receipt, so Transitive ignores it. * **What to do:** No action is necessary. ## `unsupported_message` > **Message type not stamped** The message is not an invoice, credit note, receipt or receipt reversal, so Transitive does not stamp it and created no document. * **What to do:** If the message must get a CFDI, send an invoice, a credit note, a receipt or a receipt reversal from CargoWise. ## `organization_identity_missing` > **CargoWise enterprise not named** The message does not say which CargoWise enterprise and server sent it (Enterprise ID and Server ID), so Transitive cannot tell whose it is and created no document. * **What to do:** Make sure that CargoWise sends the **Enterprise ID** and the **Server ID**. Then send the document again. ## `organization_mismatch` > **Company identity didn't match** The message names a CargoWise enterprise or company other than the one this connection belongs to, so it was not processed. * **What to do:** Make sure that the **Enterprise ID**, the **Server ID** and the company code in CargoWise match the **CargoWise** settings of the company. ## `company_unidentified` > **Company couldn't be identified** The message names no CargoWise company (DataContext, Company, Code), so Transitive cannot tell which company's document it is and there is no document to show. Transitive support is alerted. * **What to do:** Make sure that CargoWise sends the company code. Then send the document again. ## `company_conflict` > **More than one company matches** The message names more than one CargoWise company, so Transitive cannot tell which one the document belongs to and there is no document to show. Transitive support is alerted. * **What to do:** Send the document from CargoWise so that it names one company only. Then send it again. ## `company_evidence_required` > **Company not named** This connection belongs to one CargoWise company, but the message names no company (DataContext, Company, Code), so Transitive held it and created no document. Transitive support is alerted. * **What to do:** Make sure that CargoWise sends the company code. Then send the document again. ## `company_credential_mismatch` > **Another company's document** This connection belongs to one CargoWise company, but the message names a different one, so Transitive held it and created no document. * **What to do:** Send the document with the ingress credential of its own company. Or correct the company code in CargoWise. ## `company_unconfigured` > **Company isn't configured** The message belongs to a CargoWise company whose stamping is not set up yet. It is held and is processed when the company is activated in the company settings. * **What to do:** No other action is necessary. Transitive processes the message when the company is active. ## `document_number_missing` > **Document has no number** CargoWise sent an invoice, credit note or receipt without its document number (DataSource Key). Transitive identifies documents by that number, so none was created. * **What to do:** Make sure that CargoWise sends the document number. Then send the document again. ## `message_structure_invalid` > **Message structure not understood** The message is not shaped like the CargoWise document Transitive expects (for example it holds no single primary transaction), so no document was created. * **What to do:** No action is necessary. ## `document_unmappable` > **Document could not be read** Transitive could not turn this CargoWise document into a draft, so it was not processed. * **What to do:** No action is necessary. ## `ambiguous_fiscal_receipt_batch` > **Several receipts in one message** The message holds several receipts and Transitive cannot tell which one to stamp. * **What to do:** Send each receipt in its own message from CargoWise. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.