Windows Jobs Stuck Resolving Backend Variables after upgrading to v24

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

Following an upgrade to version 24.4.1, workflows were stopped, putting them in resolving variables status.

This behavior typically occurs under the following conditions:

• • A workflow is configured with a job that utilizes the :PUBLISH script statement within its Postconditions.

  • The job relies on a backend VARA that is processed by the Windows Java Agent.

  • During execution, the task remains stuck in the "Resolving Variables" or "READY FOR START" status and fails to transition to an active or running state.

  • When previewing the VARA or checking the Automic Web Interface (AWI), an error message is displayed stating: "Lines are not terminated in input text with CRLF"

Environment

Affected: 24.4.1 and 24.4.2

The issue does not occur on previous versions such as 21.0.13 or 24.3.0, affecting Java-based OS Agents

Cause

The underlying cause is that the Java agent on Windows environments does not append the CRLF (hex 0D0A) line terminator to the end of the output.

This missing line terminator results in a parsing error within the Work Process (WP)

Resolution

The fix is currently targeted for Automation Engine versions 24.4.4.