> 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/release8.2/minor-release/release8.2/known-issues.md).

# Known Issues

## askEdgi

**Issue:** During extended conversations in Discovery Mode, executing multiple prompts sequentially within the same session may gradually increase response time. As the conversation grows longer, responses may become delayed and, in some cases, may be incomplete or less relevant to the submitted prompt.

**Impact:** Users conducting long-running discovery sessions may experience slower response generation and reduced response accuracy after several consecutive prompts.

**Workaround:** Start a new Discovery Mode conversation to reset the session before continuing with additional prompts. This helps maintain response performance and relevance until the issue is addressed in a future release.

## Data Catalog

**Issue**: When downloading the Detailed Description for Table Columns after applying Equals or Not Equals filters and sorting on fields such as Certification, Critical Data Element, Environment, or Connector Type, the downloaded file may not match the filtered results displayed in the UI.

**Impact**: Users relying on exported metadata for bulk updates, validation, or reporting may receive data that does not accurately reflect the filtered list shown in the application, leading to inconsistencies during offline processing.

**Workaround**: No workaround is currently available. Verify the downloaded data against the UI before using it for bulk updates or reporting until the issue is resolved in a future release.

## Data Products

**Issue**: Saving or updating a Data Product may fail when the Description field contains lengthy content created using the Froala editor, particularly when the content includes multiple images and hyperlinks.

**Impact**: Users may be unable to save, update, or publish Data Products with large, media-rich descriptions, requiring the content to be shortened or modified before it can be saved.

**Workaround**: Reduce the size of the description by splitting the content into smaller sections or minimizing the number of embedded images and hyperlinks before saving or publishing the Data Product.

## Data Quality

**Issue:** Users may experience inconsistent access behavior when navigating to certain Data Quality resources. In specific scenarios, access restrictions may not be enforced as expected.

**Impact:** This issue may affect access control behavior for certain Data Quality resources. It does not impact the functionality of Data Quality Rules for authorized users.

**Workaround:** No workaround is currently available. Organizations should continue to follow established access control and user permission practices until this issue is resolved in a future release.

***

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/release8.2/minor-release/release8.2/known-issues.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.