Time Events execute twice randomly
Article ID: 85110
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
Error Message :
N/A
Intermittently, Event objects execute twice when they should only have been activated once.
This behavior has only been seen in Automation Engine version 9.
Investigation
To determine if this is affecting your system, you can go to the Details of the double-firing event by right-clicking on it from the Activities window, select Details, and look at the "Activator" row. If this is activated twice by the same activator (and is not set to do so either by two activations via script or two set for execution in a Schedule), this issue is present and will require further investigation by Automic.
If the issue becomes more frequent (and/or is reproducible), it should be resolved with the assistance of the Automic Customer Service / Support team.
The Automic Community article referenced below explains how to gather trace and log files required by the Automic Customer Service team for this issue.
The relevant section is the Work Process (WP) section. Communication Process (CP) and Agent can be ignored.
Tickets should contain:
Reference
N/A
Intermittently, Event objects execute twice when they should only have been activated once.
This behavior has only been seen in Automation Engine version 9.
Investigation
To determine if this is affecting your system, you can go to the Details of the double-firing event by right-clicking on it from the Activities window, select Details, and look at the "Activator" row. If this is activated twice by the same activator (and is not set to do so either by two activations via script or two set for execution in a Schedule), this issue is present and will require further investigation by Automic.
If the issue becomes more frequent (and/or is reproducible), it should be resolved with the assistance of the Automic Customer Service / Support team.
The Automic Community article referenced below explains how to gather trace and log files required by the Automic Customer Service team for this issue.
The relevant section is the Work Process (WP) section. Communication Process (CP) and Agent can be ignored.
Tickets should contain:
- The RunIDs of the Events in question
- The full set of WP log files
- The full set of WP trace files (both found by default in the Automation Engine\temp directory)
Reference
Automic Community
/articles/Knowledge/How-to-activate-a-trace-in-UNIX-Call-API-KB0011059
/articles/Knowledge/How-to-activate-a-trace-in-UNIX-Call-API-KB0011059
Environment
OS Version: N/A
Cause
Cause type:
Other
Root Cause: Unknown.
Other
Root Cause: Unknown.
Resolution
Our recommendation is to upgrade to the latest Automation Engine version 12, as there are many fixes contained between v9 and v12.
If the issue presents itself after an upgrade send Automic Support a set of rolling trace logs when the issue occurs in order to further investigate the issue.
Fix Status: No Fix
Fix Version(s):
N/A
If the issue presents itself after an upgrade send Automic Support a set of rolling trace logs when the issue occurs in order to further investigate the issue.
Fix Status: No Fix
Fix Version(s):
N/A
Additional Information
Workaround :
In the Event's "Attributes" tab, set the Tasks running parallel section to a maximum number of 1. This will stop further unwanted executions.
In the Event's "Attributes" tab, set the Tasks running parallel section to a maximum number of 1. This will stop further unwanted executions.
Feedback
Yes
No
Powered by
