Excessive Submissions of Inactive Tasks in Workflows
search cancel

Excessive Submissions of Inactive Tasks in Workflows

book

Article ID: 378127

calendar_today

Updated On:

Products

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

Issue/Introduction

Problem:

In a workflow, a task is marked as inactive both within the workflow and its object definition (General tab). Additionally, the task has the "Set Breakpoint" flag enabled in its properties.

Scenario

Workflow Execution: Upon execution, the task enters HELD status due to the breakpoint setting—this behavior is expected.
Removing Breakpoint: When the breakpoint is deleted via Right-click > Modify > Delete Breakpoint, the task correctly ends with the status Ended_Inactive—as expected.
Go Immediately Action: When selecting Right-click > Modify > Go Immediately, the task remains in HELD - Manual Stop status but repeatedly attempts to submit the job, resulting in a rapid loop. Within 20 seconds, over 1400 execution attempts occur, which is unintended behavior.

Expected vs. Actual Behavior:

Expected: The "Go Immediately" action should result in the task ending with the status Ended_Inactive since the task is inactive by definition.
Actual: Instead, the task enters a submission loop, repeatedly attempting to execute but generating only Ended_Inactive statuses. This loop continues until either the breakpoint is removed or the entire workflow is canceled.

Environment

Release: 12.x 21.x

Component: Automation Engine 

Cause

The issue has been confirmed to be a bug by our Dev team.

Resolution

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

Fix version:

Component(s): Automation Engine

Automation.Engine 21.0.9 - Available

Additional Information

Defect ID: AE-33332