> For the complete documentation index, see [llms.txt](https://docs.bluestorm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluestorm.io/support/logs-and-errors/pmiadpcdml-unable-to-classify-domain-model.md).

# PMIADPCDML: Unable to classify domain model

<table><thead><tr><th width="205"></th><th></th></tr></thead><tbody><tr><td>Error</td><td>PMIADPCDML: Unable to classify domain model.</td></tr><tr><td>Where it appears</td><td>AppControl app logs</td></tr><tr><td>Problem</td><td>When using the automatic configuration mode for a data policy, the AI service was not able to automatically classify 1 or more attributes in your domain model.<br><br>Large Language Models (LLMs) are known to have problems handling repetitive similar data inputs. If you have entity attribute names that are similar (E.g. Employee1, Employee2, Employee3) and are in the same entity, the AI service may not be able to differentiaite between them.</td></tr><tr><td>Solution</td><td>Re-check your revision from Apps Dashboard > App > Revisions. The automatica data classification process will be executed again, and because only the attributes that were not classified the first time will be submitted, the AI service may be able to correctly identify them.<br><br>If this doesn't work you will need to enable manual configuration mode for your app, and manually classify the attributes that the AI service could not classify.</td></tr></tbody></table>


---

# 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.bluestorm.io/support/logs-and-errors/pmiadpcdml-unable-to-classify-domain-model.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.