Azure job execution or file search delays using Azure BLOB Agent.

Products

• Automic Automation
• Automic SaaS

Issue/Introduction

Azure file copy or list jobs intermittently take significantly longer (between 10–50 minutes) to complete. This behavior occurs across Production, UAT, and Dev environments with no discernible pattern.

Symptoms

• Jobs hang during the file search phase for extended periods (e.g., 24 minutes).
• Agent logs show the UserServiceDriver requesting file-system information (USGFLIST) but taking hundreds of seconds to respond.
• Job reports may eventually end with "No matching files found" or "The specified blob does not exist" after the delay.
• Runid examples show total run times exceeding 20 minutes for simple file checks.

Environment

• Automic Automation 24.4.x
• Azure / Azure BLOB Agent 24.4.x

Cause

This issue is currently under investigation by Engineering under defect DE210834. It is targeted to be fixed in a future release.

Resolution

This issue is currently under investigation by Engineering under defect DE210834. It is targeted to be fixed in a future release.

To receive updates on the status of this defect, please subscribe to this article by following the steps in KB 275360.

Additional Information

Once the fix is officially released, the resolution will be updated with the specific version and download link: Download Broadcom Products and Software.