[AWI] Modifying JSCH results in an incorrect behavior whilst saving the object

Products

• CA Automic Workload Automation - Automation Engine
• CA Automic One Automation
• Automic SaaS

Issue/Introduction

Users have reported an inconsistent save experience when updating active JSCH objects. During routine edits, the system prompts a confirmation to reload active instances, aligning with expected workflow behavior. However, after acknowledging the prompt, the object does not consistently commit the changes, requiring an additional save attempt. 

Steps to reproduce:
Edit an active JSCH Object
After certain changes -- Save the Object
This results in a pop-up "Reload active instance(s) of Schedule '<JSCH_OBJECT_NAME' at the next period turnaround? "
Upon clicking Yes the pop-up disappears -- However the Object is not saved 
Clicked the Save option again in-order to save the object 

Expected Behavior: 
After making changes to an existing JSCH object --> Save --> This results in a pop-up "Reload active instance(s) of Schedule '<JSCH_OBJECT_NAME>' at the next period turnaround? " 
Clicking Yes or No should save the object. 

Actual Behavior:
After making changes to an existing JSCH object --> Save --> This results in a pop-up "Reload active instance(s) of Schedule '<JSCH_OBJECT_NAME>' at the next period turnaround? " 
Upon clicking Yes the pop-up disappears -- However the Object is not saved 
Click the Save option again in-order to save the object

Environment

Release: v24.4.x

Component: Automation Engine

Cause

DE178214

Resolution

Update to a fix version listed below or a newer version if available.

Fix version:

Component(s): Automation.Engine

Automation.Engine 24.4.4 - TBA

Additional Information

Desc:A problem was fixed on saving a Schedule. If a running Schedule is updated and saved, the Save is not reflected in UI. After reload warning is shown, schedule is saved, but the Save button is still enabled, so the saved state is not reflected in UI