> 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/patch-releases/release8.2.5.md).

# Release8.2.5

This release includes key bug fixes across Data Catalog, Data Stories, Connectors, Build Auto Lineage, and Job Workflow, improving application performance, Business Glossary navigation, Azure Data Factory lineage generation, source code export, Snowflake connectivity, and migration job execution.           &#x20;

### **Key Highlights**

* **Data Catalog:**
  * Improved application performance when navigating between modules and accessing catalog features.
* **Data Stories:**
  * Fixed errors when opening Business Glossary links from Data Stories.
* **Build Auto Lineage:**
  * Fixed lineage generation for supported Azure Data Factory pipelines.
  * Fixed authorization issues when exporting source code.
* **Connectors:**
  * Fixed Snowflake connection validation and crawling issues with key-pair authentication.
* **Job Workflow:**
  * Fixed migration workflows to trigger all required Advanced Jobs.

### **Release Details:**

<table><thead><tr><th width="117.4444580078125" align="center">Release Type</th><th width="127.25921630859375" align="center">Release Version</th><th width="321.4815673828125" align="center">Build &#x3C;Release. Build Number. Release Stamp></th><th width="148.37060546875" align="center">Build Date</th></tr></thead><tbody><tr><td align="center">Patch Release</td><td align="center">Release8.2.5</td><td align="center">release8.2.5.825.be18579</td><td align="center">October 14, 2026</td></tr></tbody></table>

## Data Catalog

### Fixed

**Application Navigation Performance**

In Data Catalog, users experienced delays when switching between modules and tabs and accessing Table Columns, Reports, and search options. The issue was caused by unnecessary role-retrieval API calls during list operations. The API calls were optimized to use pagination, reducing loading delays and improving application responsiveness.

## Data Stories

### Fixed

**Business Glossary Link Navigation**

In Data Stories, clicking an internal link to a Business Glossary term resulted in a “400 Bad Request” error, preventing users from accessing the linked term. The issue was resolved by correcting how Business Glossary URLs are handled. Users can now navigate from a Data Story to the intended Business Glossary term without encountering this error.

## Advanced Tools

### Fixed

**Build Auto Lineage: Airflow Lineage Status Accuracy**

The lineage build status for Airflow DAGs has been updated to provide accurate feedback. Previously, Python-based tasks unsupported by the regular parser displayed a "FAILED TO BUILD LINEAGE" status, incorrectly suggesting a processing error. The status handling now distinguishes between actual processing failures and unsupported code types, helping users understand the lineage build status.

**Build Auto Lineage: Azure Data Factory Pipeline Lineage**

The lineage was not generated for certain Azure Data Factory (ADF) pipelines even when source and target details were available in the Pipeline Run Parameters. The lineage builder was updated to support the required file extension and process these parameters correctly. Lineage generation now works as expected for the affected pipeline

**Build Auto Lineage: Source Code Export Authorization**

In Build Auto Lineage, users with the OE\_ADMIN role encountered an authorization error when attempting to view or export generated source code, even when the source code jobs had completed successfully. The authorization check was corrected to allow users with the appropriate permissions to access and export source code. This issue was verified as resolved in Release8.2.5.

## Connectors

### Fixed

**Snowflake Connector – Fixed Connection Validation and Crawling Issues**

In Connectors, Snowflake connections using key-pair authentication encountered errors during validation, crawling, and data profiling after upgrading to Release8.2.3. The issue was addressed, and these operations were verified to work as expected in Release8.2.5.

## Job Workflow

### Fixed

**Migration Job Workflow Execution**

In Job Workflow, migration workflows triggered only two jobs instead of all the required migration jobs when upgrading from earlier versions to Release 8.2.x. Incorrect version-matching conditions prevented eligible jobs from being included in the workflow. The migration job conditions were corrected to ensure all required Advanced Jobs trigger as expected during the upgrade process.

***

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/patch-releases/release8.2.5.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.
