Limited Cancellation Logging for Jobs with the status "waiting for the host of an agentgroup"

Products

• CA Automic Workload Automation - Automation Engine
• Automic Automation
• Automic SaaS

Issue/Introduction

You may notice that canceling a job with the status "waiting for the host of an agentgroup" fails to generate information in the activation or logging reports․​‌​‌​‌‍​‌‍​‌‍‍

Whereas if you cancel a job "Waiting for Host" logs an error message within the log files.

Example:

Upon cancelling a job with the status - Waiting for the host of an AgentGroup.

Activation Log:
2026-02-11 08:07:51 - U00005014 AgentGroup '<AGENT_GROUP_X>', client '22', version '2' has been resolved.
2026-02-11 08:07:51 - U00005016 AgentGroup '<AGENT_GROUP_X>', client '22': host '<Agent_name>' is not active.

Logging: 
<Empty>

Upon cancelling a job with the status "Waiting for Host"

Logging:
2026-02-11 08:06:01 - U00011113 Task with RunID 'xxxxxxxxxx' will be re-started as soon as host '<Agent_name>' is active again or the previous error has been corrected.
2026-02-11 08:06:08 - U00011051 User 'USER/DEPT' initiated CANCEL for '<jobname>' (RunID:  'xxxxxxxxxx').

IMPACT: Users cannot track who canceled a job or identify the cancellation reason through standard reporting when Agent Groups are involved.

Environment

Release: v21.x v24.x

Component: Automation Engine

Cause

DE182531

Resolution

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

Fix version:

Component(s): Automation.Engine

Automation.Engine 24.4.5 - Planned release June 2026