> For the complete documentation index, see [llms.txt](https://sitecoreuml.gitbook.io/sitecoredxg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sitecoreuml.gitbook.io/sitecoredxg/how-to/viewing-helix-validation-errors.md). # Viewing Helix Validation Errors As of SitecoreDXG 1.1.0, the new Helix Validation features have been implemented and validation errors can be reviewed in several ways. ### Diagrams Invalid dependencies are automatically colored "red" in your diagrams. If a red dependency is displaying, view the dependency for more details. If you are looking at a [Layer Diagram](/sitecoredxg/about-the-generated-documentation/diagrams/layer-diagrams.md) or a [Module Diagram](/sitecoredxg/about-the-generated-documentation/diagrams/module-diagrams.md) and you are unsure of the source and target templates of the dependency then refer to the [Layer and Module Dependency Models](/sitecoredxg/how-to/viewing-helix-validation-errors.md#layer-and-module-dependency-models) section below for more. ### Layer and Module Dependency Models On the documentation page for the [Dependency Model](/sitecoredxg/about-the-generated-documentation/models/dependencies.md) that lives under the layer, e.g. `(Feature->Feature)`, or module, e.g. `(Multisite->Multisite)`, you can see all dependencies contained in the layer/module, including any invalid dependencies. Any entries with the `INVALID:...` prefix are invalid and will state the reason why the dependency is invalid, as well as the source and target template path information to help you track down the offending template(s). ### Dependency Models On the model for the dependency itself you can see the same `INVALID:...` documentation for the dependency that you find on a [Layer or Module dependency model](/sitecoredxg/how-to/viewing-helix-validation-errors.md#layer-and-module-dependency-models). ### Slack and Microsoft Teams Notifications The completion handlers for Slack and Microsoft Teams natively display any validation errors detected during generation in the generation completion notifications that they send. For more information, refer to the [Slack integration](/sitecoredxg/how-to/slack-and-ms-teams-integration/integrating-with-slack-via-webhooks.md) and [Microsoft Teams](/sitecoredxg/how-to/slack-and-ms-teams-integration/integrating-with-ms-teams-via-webhooks.md) integration documentation pages. ### Custom Remember that SitecoreDXG was designed specifically with extensibility in mind. All detected validation errors are passed to the completion handlers via the `metaball` parameter, thus you can create your own custom error handling logic that runs after generation has completed by [creating a custom completion handler](/sitecoredxg/how-to/creating-a-custom-completion-handler.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 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://sitecoreuml.gitbook.io/sitecoredxg/how-to/viewing-helix-validation-errors.md?ask=&goal= ``` `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.