> 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.3.md).
# Release8.2.3
This release introduces key enhancements and bug fixes across Home and Connectors, improving widget consistency, environment-specific metadata and lineage extraction, profiling stability, and column mapping accuracy.
**Key Highlights**
* **Home**: Fixed an issue where deleted Data Stories remained visible as Home Page widgets and in widget management, ensuring deleted stories and their associated widgets are removed completely.
* **Connectors**:
* **DBT Cloud**: Added environment-specific manifest selection, enabling independent crawling of UAT, PROD, DEV, and other environments within the same DBT Cloud project while maintaining accurate metadata and lineage.
* **HubSpot**: Resolved intermittent profiling failures through the Bridge, ensuring HubSpot objects are processed successfully after schema crawling.
* **QuickSight**: Fixed column mapping issues in Custom SQL datasets, ensuring data is consistently assigned to the correct fields.
**Release Details:**
| Release Type | Release Version | Build<Release. Build Number. Release Stamp> | Build Date |
|---|
| Patch Release | Release8.2.3 | release8.2.3.823.da64cdf |
September 15, 2026 |
## Home
### Fixed
**Removed Deleted Data Stories from Home Page Widgets**
In Home, an issue where a deleted data story remained visible as a Home Page widget and under Security > Manage Home Page Widgets has been resolved. When a data story was added as a Home Page widget and then deleted from Data Stories, the story was removed from the Data Stories page but continued to appear in the Home Page widget and widget management list.
The deletion process has also been corrected to remove the associated Home Page widget.
## Connectors
### New & Improved
**DBT Cloud Connector: Environment-Specific Manifest Selection**
The DBT Cloud connector now supports crawling multiple environments, such as UAT and PROD, independently when they use the same DBT Cloud project. This ensures that the manifest and corresponding metadata and lineage are retrieved from the appropriate environment.
The following enhancements have been implemented:
* Added an optional DBT Environment attribute to the connector configuration.
* Customers using multiple environments for the same DBT Cloud project can configure separate OvalEdge connector instances and specify the corresponding environment for each instance.
* The connector uses the configured DBT Environment value to identify successful runs and select the latest successful run within the specified environment.
* UAT, PROD, DEV, and other environments can be crawled independently, with their corresponding metadata and lineage maintained separately.
* When the DBT Environment is left blank, the connector retains the existing behavior of selecting the latest successful run without environment filtering.
This enhancement ensures that the correct environment-specific manifest is used during crawling, allowing metadata and lineage from multiple DBT Cloud environments to be captured accurately.
### Fixed
**Resolved HubSpot Profiling Failures Through Bridge**
In the HubSpot Connector, an issue where profiling intermittently failed with a remote method exception when executed through the Bridge has been resolved. Schema crawling completed successfully, but profiling failed for individual HubSpot objects.
The profiling process has been fixed to ensure these objects are processed successfully through the Bridge.
**Resolved Column Mapping Issues in QuickSight**
In QuickSight, an issue where columns in Custom SQL datasets mapped to incorrect fields has been resolved. The column mapping could become misaligned, causing data to appear under the wrong columns.
The mapping has been corrected to ensure data is consistently assigned to the appropriate columns.
***
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.3.md?ask=&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.