--- title: "Crescendo 6.3.1.2 Patch 42" slug: "crescendo-6-3-1-2-patch-42" status: "update" updated: 2026-10-01T04:27:22Z published: 2026-10-01T04:27:22Z canonical: "help.symphonysummitai.com/crescendo-6-3-1-2-patch-42" --- > ## 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. # Crescendo 6.3.1.2 Patch 42 > [!NOTE] > 🎯 Now Live! > > **Release Date | 30**th **September 2026** ## Fixed Issues The following are the issues fixed in Crescendo 6.3.1.2 Patch 42. | Issue ID | Issue Description | Resolution | | | --- | --- | --- | --- | | 193164 | In the **Discovery** module, subnet mask software details were not captured because the hardware and software discovery calls were triggered in parallel. Software discovery started before the hardware discovery was completed, causing the hardware details validation to fail. | Subnet mask software details are captured. Hardware discovery completes successfully before software discovery begin. | | | 191466 | Some emails remained unread in the mailbox and were not converted into tickets, even though they were received in the service desk mailbox. | All the emails received in the service desk mailbox were successfully converted into tickets. | | | 193054 | Multiple SLA IDs were being captured for parent-child tickets in the im_d_sla_manageincidents table, resulting in incorrect SLA associations and inconsistencies in SLA tracking for linked incidents. | Only the appropriate SLA ID is captured and maintained for parent-child ticket relationships in the im_d_sla_manageincidents table | | | 193558 | The Software Details GET API did not return any data and displayed **"No records found"**, even though records were present in the database. | The Software Details GET API now returns the data and does not display any error. | | | 193222 | The **?** character was not accepted in the field name of a **Radio Button** field when creating an SR catalog form, preventing the field from being saved. The same character was accepted in a **Multi-Select Dropdown** field. | **Radio Button** fields with the **?** character in the field name can be saved successfully | |