DB Event remains in Sleeping status after Max Runtime (MRT) timed out

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

A DB Event integrated into a Workflow intermittently remains in a Sleeping status within Process Monitoring after the set Maximum Runtime (MRT) has been exceeded.

While the task within the Workflow correctly transitions to ENDED_TIMEOUT and the workflow continues to successor Tasks, the child Event execution remains active and must be manually cancelled.

Cause

This behavior is caused by a race condition identified under DE184510

Resolution

Solution:

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
Automation.Engine 24.1.0 - Planned release June 2026

Additional Information

A problem has been fixed that prevents a DB Event from being inactive after a timeout.