File Event remains in status 'Checking'

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

File Event jobs are moving to Checking state instead of Sleeping and do not trigger the jobs.

File events in Automic Automation become stuck in a perpetual 'Checking' state after upgrading from v21.0 to v24.4. This occurs specifically when the file/path target is configured with wildcard patterns (e.g., via a variable containing a wildcard like `path/to/file*.txt`).

Symptoms include:

• no progression to 'Sleeping' state
• absence of 'Next Check' timestamp
• lack of ongoing logging reports (only the Activation logs is present)

Events do trigger correctly when the expected file is dropped, but with a ~1-minute stability delay, making them appear frozen.

Non-wildcard single-file configurations work normally, cycling between states with full logging. The issue affects both Windows and Unix agents 

Cause

DE178900

Resolution

This will be fixed in a future version.