AWA: Jobs in 'waiting for predecessor' can not be cancelled via CANCEL_UC_OBJECT or cancel in the user interface.
Article ID: 191492
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
When attempting to cancel a job in 'waiting for predecessor' (status 1700) via CANCEL_UC_OBJECT or cancelling within the Automic Web Interface, the operation fails stating this is not a cancelable status.
Environment
Component : AUTOMATION ENGINE
Cause
As designed. The cancel command only applies to objects in an active status:
Return Codes: 1300, 1310, 1510, 1520-1521, 1529-1531, 1540-1542, 1545-1546, 1550-1551, 1554, 1557-1558, 1565, 1566-1576, 1578-1584, 1600, 1650-1653, 1701, 1704-1705
Waiting for predecessor, although the task has been activated, is in a blocked status within the system.
Return Codes: 1300, 1310, 1510, 1520-1521, 1529-1531, 1540-1542, 1545-1546, 1550-1551, 1554, 1557-1558, 1565, 1566-1576, 1578-1584, 1600, 1650-1653, 1701, 1704-1705
Waiting for predecessor, although the task has been activated, is in a blocked status within the system.
Resolution
Documentation will be updated to explicitly add Active vs the current 'activated' to CANCEL_UC_OBJECT
To successfully run cancel commands, utilize the cancel on the workflow containing the tasks, versus the tasks themselves.
To successfully run cancel commands, utilize the cancel on the workflow containing the tasks, versus the tasks themselves.
Feedback
Yes
No
Powered by
