S3 Monitor Jobs fail to match files when using a prefix in the regex pattern

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

• An S3 Monitor File Job fails to detect files when a prefix is defined in the source file path regex (e.g., abc.*\.csv).
• The same regex pattern works as expected in S3 Download Jobs.
• Monitoring works only when the regex is simplified to the extension alone (e.g., .*\.csv), but fails when combined with a specific filename prefix.
• The job report shows the regex is validated but the execution fails to identify matching objects in the S3 bucket despite them being present.

Environment

Product: CA Automic Workload Automation

Component: S3 Agent (RA FTP S3)

Version: 24.5.0

Cause

DE184188

Resolution

This issue is resolved in the following component versions:

• Plugin.Extension.S3 (S3 Agent) version 24.5.2 or higher.
• Integration.S3 version 1.2.1 or higher.

Workaround: If an immediate upgrade is not possible, use a broader regex pattern (e.g., .*\.csv) and manage file filtering at the workflow level, or ensure the Query Parameter: Prefix field in the job definition matches the fixed portion of the filename exactly, leaving only the variable portion for the regex field.