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

# Release7.2.4.3

This release introduces fixes in the Advanced Jobs module, improving job execution efficiency and overall system performance during post-migration activities.

**Key Highlights**

* **Advanced Job Performance Improvement**: Fixed an issue where the Update WikiText to store plain text job ran for a long time during post-migration.

**Release Details:**

<table><thead><tr><th width="135">Release Type</th><th width="145.3333740234375">Release Version</th><th width="349">Build &#x3C;Release. Build Number. Release Stamp></th><th>Build Date</th></tr></thead><tbody><tr><td>Hotfix Release</td><td>Release7.2.4.3</td><td>Reelase7.2.4.3.724344b556e</td><td>15th Dec 2025</td></tr></tbody></table>

## Advanced Job

### Fixed

**Advance Job Performance Issue in Update WikiText**

In the **Advanced Job** module, an issue occurred where the Update WikiText to store plain text job ran for an extended duration during the post-migration upgrade process and did not complete as expected. The issue occurred due to inefficient query execution while processing the wiki content. The issue has been resolved through query optimization, and the job now completes successfully with improved performance.

***

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.4.x/release7.2.4.3.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.