Stop for modification and start does not work as expected

book

Article ID: 84924

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine AUTOMIC WORKLOAD AUTOMATION

Issue/Introduction

Error Message :
N/A

A Workflow runs. The workflow monitor is opened and via the button Modify, the workflow is stopped for modification:
 

<Please see attached file for image>

0EMb0000001Uv1e.png
Now the workflow can be modified (or not, that does not change the test). Afterwards, the button Modify is clicked again. The pop up says, the WF is set back to active:
 

<Please see attached file for image>

0EMb0000001Uv1o.png
However, the WF does not start again. In Process Monitoring, the WF is still stopped:
 

<Please see attached file for image>

0EMb0000001Uv1t.png

Expected behavior is, that in this case, the WF starts again, but ist must be set to Go manually:
 

<Please see attached file for image>

0EMb0000001Uv1y.png

Cause

Cause type:
Defect
Root Cause: Misleading message after modification of a workflow in monitoring, suggesting that the workflow is now active (thus running) again. This is false as in fact the workflow is still paused and it needs to be started manually.

Environment

OS Version: N/A

Resolution

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

Fix Status: Released

Fix Version(s):
Automation Engine 12.1.0 - Available
Automation Engine 12.0.3 - Available

Additional Information

Workaround :
In Process Monitoring, right click and select Go:
 

<Please see attached file for image>

0EMb0000001Uv23.png

Attachments

1558693256794000084924_sktwi1f5rjvs16m54.png get_app
1558693254924000084924_sktwi1f5rjvs16m53.png get_app
1558693253133000084924_sktwi1f5rjvs16m52.png get_app
1558693251390000084924_sktwi1f5rjvs16m51.png get_app
1558693249433000084924_sktwi1f5rjvs16m50.png get_app