> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release7.2/hotfix-releases/release7.2.4.x/release7.2.4.8.md).

# Release7.2.4.8

This release introduces targeted fixes across Data Catalog, and Lineage modules, improving reliability, accuracy, and system stability.

**Key Highlights**

* LMDF Upload Validation for Governance Roles
  * Fixed incorrect validation errors for optional governance role fields so LMDF uploads now complete successfully.
* Build Lineage Job Memory Failure
  * Fixed a memory issue that caused lineage builds to fail when processing all items together.

**Release Details:**

<table><thead><tr><th width="137.333251953125">Release Type</th><th width="155.6666259765625">Release Version</th><th width="351.6666259765625">Build &#x3C;Release. Build Number. Release Stamp></th><th>Build Date</th></tr></thead><tbody><tr><td>Hotfix Release</td><td>Release7.2.4.8</td><td>Release7.2.4.8.7248fc51cee</td><td>2nd Feb 2026</td></tr></tbody></table>

## Data Catalog

### Fixed

**LMDF Upload Validation for Governance Roles**

In the Data Catalog module, an issue occurred where optional governance role fields triggered validation errors during LMDF uploads, causing jobs to complete with partial success. The issue has been resolved, and now optional governance role fields no longer block uploads, allowing LMDF jobs to complete successfully.

## Lineage

### Fixed

**Build Lineage Job Memory Failure**

In the Lineage module, an issue occurred where the Build Lineage job failed due to memory limitations when processing all codes together, impacting lineage generation. The issue has been resolved, and now lineage builds complete successfully without memory failures during full processing.

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.


---

# 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.ovaledge.com/release7.2/hotfix-releases/release7.2.4.x/release7.2.4.8.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.