> 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/freemium/installation-guide/go-live.md).

# Go-live

Before you go-live, you should have done these steps;

* Configures business Central according to the guide.
* Made a test case to make sure you are sending out emails with PDFs correctly.
* Updated the customer cards according to the guide.
* **Optional -** [Enable Order Confirmations](/freemium/pdf-order-confirmation/untitled.md) to be sent out via email PDFs.

If all of above is done, and you are ready to go-live, go back to 'Job Queue Entries' in Business Central and **restart** the '**GEDIQUEUE**' and '**GEDIDELETE**' job queues to start processing queued messages in our app.

{% hint style="info" %}
If you for some reason wants to stop or pause the automatic processing in the future, you should set 'Job Queue Entry' 'GEDIQUEUE' and 'GEDIDELETE' to 'Set On Hold'. You can restart it whenever you want to enable it again.
{% endhint %}

{% hint style="danger" %}
The user that restarts the Job Queue Entry must have user permissation set 'SUPER' or 'GEDI ADMIN FULL'.
{% endhint %}

Follow up on your first invoices after this and make sure their GEDI status reaches 'PDF Sent', as described in the [invoice process.](/freemium/user-guide/invoice-process.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.goldenedi.com/freemium/installation-guide/go-live.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.