> For the complete documentation index, see [llms.txt](https://docs.goldenedi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.goldenedi.com/standard-app-core-concepts/concepts/gedi-messages-queue.md).

# GEDI Messages Queue

![GEDI Message Queue](/files/usDmQMp0QxkVmbS6lTqi)

## Introduction

In the 'GEDI Message Queue' page view in Business Central you will find 'GEDI Messages'. A 'GEDI Message', is something that will be or has been processed within the Standard App<mark style="color:red;">.</mark>&#x20;

There are different types of 'GEDI Messages', for example exports, imports, control functions, emails, status updates and much more. The exact function of each 'GEDI Message' is defined by a 'GEDI Message Code'.

In the 'GEDI Message Queue' page view it is possible to manually process, reprocess or run 'GEDI Messages' for testing purpose. &#x20;

'GEDI Messages' can be automatically deleted by a Job Queue Entry. This clean up is making sure that the 'GEDI Message Queue' doesn't store too much data. This is to make sure that we don't have negative impact on performance over time.

'CIP Work Items' are read or written to the Standard App as 'GEDI Messages' holding a unique 'Work Item' ID. The 'CIP Work Item' ID acts as a link between the two layers; Business Central and the CIP.


---

# 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:

```
GET https://docs.goldenedi.com/standard-app-core-concepts/concepts/gedi-messages-queue.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
