> For the complete documentation index, see [llms.txt](https://docs.dorg.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dorg.pro/install-dorg/troubleshooting/conversation-logs.md).

# Conversation logs

Logs of recent conversations between users and your Dorg are accessible through a web interface at:

<https://api.\\><your-dorg-domain>/debug/execution

Replace `<your-dorg-domain>` with your actual DORG domain (e.g., `api.michael.contoso.com/debug/execution`).

For each interaction between a user and the DORG, this view displays:

* **Initial prompt** -- the original user request that triggered the interaction
* **Orchestrator reasoning flow** -- the step-by-step reasoning chain, including intermediate decisions and tool calls made by the orchestrator during processing
* **Final output** -- the response delivered back to the user

This interface is useful for understanding how the orchestrator interpreted a request, which tools and data sources were invoked, and diagnosing unexpected or incorrect responses.


---

# 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://docs.dorg.pro/install-dorg/troubleshooting/conversation-logs.md?ask=<question>&goal=<endgoal>
```

`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.