> For the complete documentation index, see [llms.txt](https://kb.bevica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bevica.com/documentation/integration/bevica_warehouse_integration/communication_engine_messages.md). # Communication Engine Messages View and troubleshoot messages processed by the Communication Engine. {% hint style="warning" %} **Prerequisites** Bevica Warehouse Integration extension installed. Communication Engine extension installed. Account with a Vision managed warehouse: LCB, Vinotheque, Lanchester, EHD, Coterie Vaults. {% endhint %} ### Communication Engine The communication engine is a solution framework to enable the communication of data between Bevica and various endpoints such as a Vision warehouse. It is used for the following Vision warehouse integrations: * [Dispatch Notifications](/documentation/integration/bevica_warehouse_integration/warehouse_outbound_document_integration.md) (Outbound) * [Pre-advices](/documentation/integration/bevica_warehouse_integration/warehouse_pre-advice_integration.md) (Outbound) * [Stock Reconciliation](/documentation/integration/bevica_warehouse_integration/warehouse_item_reconciliation.md) (Inbound) * [Stock Received Notifications](/documentation/integration/bevica_warehouse_integration/warehouse_goods_received_integration.md) (Inbound) * [Pick Confirmations](/documentation/integration/bevica_warehouse_integration/warehouse_pick_confirmation_integration.md) (Inbound) ### Communication Engine Messages #### **Message Generation and Processing** When you send or receive files using the communication engine, a communication engine message is created. * Outbound Requests - a communication engine message is created when the outbound request is generated and sent. It will be sent to Vision when the communication engine is run. * Inbound Requests - a communication engine message is created and processed when the communication engine is run. This will create a Warehouse Inbound Request record. #### **Message Status** You can view the messages from the Communication Engine Route page; there are columns for No. of Messages Pending, Errored or Completed. ![Communication Engine Routes showing pending, errored, and completed message counts](https://2932934759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfUgpGDVvyqBWVvwVIy9a%2Fuploads%2Fgit-blob-85f3f95970a1343bb77bb6cde730fb9beab60c87%2FuEpGmdfaRyyp2nbN9fOetqjb7QQbEt9jcg.png?alt=media) Each communication message has a status: * Pending - initial value for a new message to process * Posted - message has completed successfully * Errored - the sending or receiving of the message has failed * Cancelled - if an outbound message hasn't yet been sent it can be cancelled, see below #### **Viewing Message details** It is possible to view the Outbound and Inbound message between Bevica and Vision. * For outbound requests the outbound message is the file sent to Vision and is the same as inspecting the request from the outbound request page. The inbound message is the response received from Vision. * For inbound requests the inbound message is the relevant file received from Vision. ![Communication Engine message details showing inbound and outbound payloads](https://2932934759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfUgpGDVvyqBWVvwVIy9a%2Fuploads%2Fgit-blob-254a72fd29199105e9254c173de03dee8355ac42%2FmdVFktXu6HKTm-usM0WRmGSh1iROce92ZQ.png?alt=media) #### **Cancelling Messages** If you would like to cancel an outbound message before it is sent, from the Communication Engine Route page, drill down on the No. of Pending Messages, click on the message you'd like to cancel and select **Set Status Cancelled** in the ribbon. If you have cancelled a message by mistake, you can view that message by searching for Communication Engine Messages and select **Set Status Pending**. ![Communication Engine Messages list showing a message status change action](https://2932934759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfUgpGDVvyqBWVvwVIy9a%2Fuploads%2Fgit-blob-c29aa3dfc14a01c50445dfd5c6c8ff9bead3a9f4%2FTGGX5fU3zHF1nsvhsRKuDIm5snVkmsporw.png?alt=media) ### Message Errors #### **Outbound Requests** When sending a communication engine message to the warehouse, if Vision returns a response other than 200, both the message status and the Comm. Engine Status field on the outbound request page will change to Errored. You are able to see the detail of the error in the Error Message field on the communication engine message, or the Comm. Engine Error on the outbound request. Depending on the error you can either amend the sales, transfer or purchase order, or try sending the file again. If there is a **connection error** on the communication engine, you can resend the existing message again: * From the **Communication Engine Route** page, drill down on **No. of Messages with Error**. * In the ribbon, select **Set Previous Status**. This will set the status back to Pending and put the message into the No. of Messages Pending column. * The job queue will process the record/s the next time it is run. Or select **Run Communication Engine** to process them manually. If it is a **data error** and the sales, transfer or purchase order still exists you can make the relevant changes and recreate the outbound request: * Go to the outbound request page, find the entry relating to the sales, purchase transfer order and select **Cancel Request** in the ribbon twice. This will set the request to Cancelled. * Go to the sales, transfer or purchase order, make the necessary changes, release the order and select Actions, Warehouse, **Add Whse. Request** if a request wasn't created on release. The order will appear as a Pending order in the outbound request list. Process the same as the original request, either manually or via the job queues. #### **Inbound Requests** Inbound requests have a maximum number of times that you are able to retrieve the file in 24 hours. If you try more times Vision will return an error. If you receive an error saying the user has exceeded the limit then try again the following day. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://kb.bevica.com/documentation/integration/bevica_warehouse_integration/communication_engine_messages.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.