> For the complete documentation index, see [llms.txt](https://docs.dynalogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dynalogic.com/birds-document-warehouse-product-overview/troubleshooting-and-known-issues.md).

# Troubleshooting and Known Issues

Start with the symptom and the application in which it occurs. Document Warehouse permissions, external-system user mappings, connector settings, and integration logs can all affect document access or processing.

## Document Warehouse access and configuration

The [Document Warehouse FAQ](https://docs.dynalogic.com/birds-document-warehouse-product-overview/troubleshooting-and-known-issues/warehouse-faq.md) covers tenant access, roles, missing configuration screens, fields, templates, taxonomy, and external-system visibility. Check the user's email address, tenant membership, and role before assuming that a document is missing.

## Finance and Operations

The [Finance and Operations FAQ](https://docs.dynalogic.com/birds-document-warehouse-product-overview/troubleshooting-and-known-issues/faq.md) covers the Document Warehouse entry point, integration access, entity mappings, and timeouts. For printing issues, consult [Adobe Acrobat for PDF printing](https://docs.dynalogic.com/birds-document-warehouse-product-overview/troubleshooting-and-known-issues/adobe-acrobat-for-pdf-printing.md).

## Customer Engagement

The [Customer Engagement FAQ](https://docs.dynalogic.com/birds-document-warehouse-product-overview/troubleshooting-and-known-issues/faq-1.md) covers entity configuration. Use [Integration logs](https://docs.dynalogic.com/birds-document-warehouse-product-overview/d365-customer-engagement/integration-logs.md) when investigating failed or unexpected integration behavior.

## Collect useful diagnostic information

Record the tenant, affected application, user, time of the failure, action being performed, and the exact error message. Do not include passwords, external-system secrets, authentication tokens, or confidential document contents in a shared diagnostic report.


---

# 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.dynalogic.com/birds-document-warehouse-product-overview/troubleshooting-and-known-issues.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.
