> 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.9.md).

# Release7.2.4.9

This release introduces fixes across the Job, Impact Analysis, and Lineage modules. These updates correct job behavior, align permission handling, and ensure reliable lineage generation.

Key Highlights

* **Search Job Triggered During Crawl and Profile**\
  Resolved job behavior when triggered from the connection page and ensures metadata remains consistently visible during execution.
* **Author Users Unable to Add Objects in Impact Analysis**\
  Resolved permission restrictions and enabled author users to add and delete objects in impact analysis without errors.
* **Lineage Warnings in Power BI Cloud**\
  Addressed warning messages during lineage processing and ensured lineage is generated successfully for the affected scenarios.

**Release Details:**

<table><thead><tr><th width="136.6666259765625">Release Type</th><th width="160.3333740234375">Release Version</th><th width="348">Build &#x3C;Release. Build Number. Release Stamp></th><th>Build Date</th></tr></thead><tbody><tr><td>Hotfix Release</td><td>Release7.2.4.9</td><td>Release7.2.4.9.72493c471f</td><td>13th Feb 2026</td></tr></tbody></table>

## Jobs

### Fixed

**Search Job Triggered During Crawl and Profile**

In the Job module, the system automatically triggered the search job when the user clicked the Crawl/Profile button on the connection page. While the job was running, the metadata was temporarily not visible in the Data Catalog. The issue has been resolved, and the system now keeps metadata consistently visible with proper job handling during crawl and profile operations.

## Impact Analysis

### Fixed

**Author Users Unable to Add Objects**

In the Impact Analysis module, author users were unable to add objects to impact analyses due to permission restrictions, resulting in errors when adding objects directly or from the data catalog. The issue has been resolved, and now author users can add and delete objects in impact analysis without permission errors.

## Lineage

### Fixed

**Lineage Warnings in Power BI Cloud**

In the Lineage module, warning messages appeared during auto lineage processing for the Power BI Cloud connector during lineage build. Lineage was not generated for specific tables during processing. The issue has been resolved, and now lineage builds successfully for the affected scenarios without warning messages and without impact on other modules.

***

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