> 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.3.x/release7.2.3.2.md).

# Release7.2.3.2

This release includes key fixes across Advanced Jobs and User Management, improving image handling in Data Stories Migration.

**Key Highlights**

* **Advanced Jobs**: Fixed an issue in the Data Stories Migration job where images were not downloaded correctly, resulting in broken or missing visuals after upload. Images now download and display properly.

**Release Details:**

<table><thead><tr><th width="137.66668701171875">Release Type   </th><th width="140.33331298828125">Release Version</th><th width="355.33331298828125">Build &#x3C;Release. Build Number. Release Stamp></th><th>Build Date</th></tr></thead><tbody><tr><td>Hotfix Release</td><td>Release7.2.3.2</td><td>Release7.2.3.2.723257d33b4</td><td>18th Nov 2025</td></tr></tbody></table>

## Advanced Jobs

### Fixed

**Image Display Issue in Data Stories Migration**

In the 'Data Stories Migration' Advanced Job, an issue occurred where images were not downloaded correctly, resulting in broken or missing images after upload. This issue has been resolved, and images now download and display correctly.

***

Copyright © 2025, 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.3.x/release7.2.3.2.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.