ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
CA Automic Workload Automation: STOP NOMSG is used but the result is not ENDED_EMPTY as documented
Article ID: 110993
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
The error is described by the following example:
However, the result is always ENDED_OK as in the example below:
In the Event Process of a Time Event, the script function :STOP NOMSG is used to stop the execution of the Event Process. E.g. if a time criterion is not fulfilled.
According to documentation, objects stopped with :STOP NOMSG should always end with the status ENDED_EMPTY:
According to documentation, objects stopped with :STOP NOMSG should always end with the status ENDED_EMPTY:
<Please see attached file for image>
However, the result is always ENDED_OK as in the example below:
<Please see attached file for image>
Cause
An error has been fixed where !EVNT tasks did not end with status "ENDED_EMPTY" if :STOP NOMSG is used in !PROCESS tab.
Environment
Release: AUTWAB99000-12.2-Automic Workload Automation-Base Edition
Component:
Component:
Resolution
Please install a fixed version as soon as available, or a newer version:
- Automation Engine 12.1.3
- Automation Engine 12.2.1
- Automation Engine 12.3.0
Attachments
Feedback
Yes
No
Powered by
