Jobs are stuck in "Start Initiated" while using Proxy

Products

• Automic SaaS
• Automic Automation

Issue/Introduction

This article addresses an issue where Automic jobs remain in a "Start Initiated" status. This behavior occurs when jobs are submitted, but the status is not correctly synchronized back to the Automic system due to a proxy connection handling defect. This issue specifically impacts environments utilizing the Automic Proxy.

Note: This intermittent issue has been observed in connection with RA agents.

Environment

Release: v24.x v26.x

Component: Automation Engine

Cause

The issue is currently being investigated by engineering

Resolution

To stay updated on the status of this topic, please subscribe to this article by following the steps in: How to subscribe to Knowledge Base articles.

If you require further assistance or if the issue persists after applying the workaround, please contact Broadcom Support. See Contact Support to reach a Support Engineer in your region.