---
title: "Release Notes Apex Aspen Q2 Patch 5"
slug: "release-notes-apex-aspen-q2-patch-5"
status: "update"
updated: 2026-08-13T06:16:26Z
published: 2026-08-13T06:16:26Z
canonical: "help.symphonysummitai.com/release-notes-apex-aspen-q2-patch-5"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.symphonysummitai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Release Notes Apex Aspen Q2 Patch 5

> [!NOTE]
> 🎯 Now Live!
> 
> **Release Date | 13th August 2026**

The following section provides fixed issues in Apex Aspen Q2 Patch 5 release.

- [Fixed Issues](/apex/docs/release-notes-apex-aspen-q2-patch-5#fixed-issues)

### Fixed Issues

Following are the fixed issues in this release.

| Issue ID | Issue Description | Resolution |
| --- | --- | --- |
| 191874 | In the Knowledge Management workflow, when the **Level 2 approver** selected **Refer Back** for a Knowledge record, the record status incorrectly remained **Authorized** instead of changing to **Refer Back to Author**. Additionally, the Refer Back details were blank in the triggered notification email. | When the Level 2 approver selects **Refer Back**, the Knowledge record status is updated to **Refer Back to Author**, and the Refer Back details are displayed in the triggered notification email. |
| 191148 | The Instance dropdown in the **Create Workflow** popup displayed instance details belonging to another customer, such as Customer A, when creating a workflow for the Customer B in the **Problem Management** module. | The Instance dropdown displays only the relevant customer instance when creating a workflow. |
| 190822 | **Service Request** status values were inconsistent between the **Service Request** List and the Custom BI Service Request Dump. In some cases, the BI report displayed outdated statuses such as New or In-Progress instead of the current Resolved status. The **Pending For Approval** (Refer Back) status was also not displayed consistently in the BI report. | **Service Request** statuses are displayed consistently in the **Service Request List** and **Custom BI Service Request Dump**, including the **Pending For Approval** (Refer Back) status. |
| 190439 | CC users did not receive notifications when updates were added to tickets, even when they were included in the CC list through the Address Book. | CC users receive notifications for ticket updates when they are included in the CC list |
| 191080 | The classification-specific attribute bar was displayed in a minimized state, preventing users from selecting the icon when creating a CI with Server or Network classification. | The classification-specific attribute bar is getting displayed as expected, and not in a minimized state, allowing users to select the icon when creating a CI with Server or Network classification. |
| 190940 | The systems were reporting in **AM_Agent_OnlineStatus** and were visible in **Hardware Discovery**, but the **Discovery and Agent Status Dashboard** Report still showed them as **Offline** with an incorrect **Contacted Date**. | The **Discovery and Agent Status Dashboard** Report displays the correct **Contacted Date**. |
| 189622 | When a user updated an existing assigned or unassigned Service Request by email, Analysts received two emails (duplicate) instead of one. | When a user updated an existing assigned or unassigned Service Request by email, Analysts received only one email and not the duplicate emails. |
| 191172 | Categories configured as **Disable for End User** continued to appear in the **Category** field when an end user created an incident. | Categories disabled for end users are now excluded from the Category field on the **Create Incident** page. |