RA REST job fails | U01001307 A variable name with the length x is not allowed.

Products

• CA Automic Workload Automation - Automation Engine
• CA Automic One Automation

Issue/Introduction

When A RA Webservice REST Job fails with the following error:

• U00021719 Syntax error in object 'JOBS.JOBNAME', line '00000'. 'U01001307 A variable name with the length x is not allowed.'

In case cases the job runs if restarted.

This can also happen when running a RA Webservices REST job submitted via a recurring execution (C_PERIOD), where the job may intermittently fail with the following syntax errors:

• U01001303 Invalid variable name '1'. Begin with a letter or valid special character.
• U01001307 A variable name with the length 0 is not allowed.

Cause

This issue is caused by a misconfiguration in the Response tab of the job object combined with limitations of the older RA REST Agent (v4.6 and earlier). The older agent allowed or required an ampersand (&) prefix in the Output Name field (e.g., &PRIMARY#), which causes parsing conflicts during certain execution cycles like C_PERIOD.

Resolution

There are two ways to resolve this issue: a manual workaround for existing objects or a permanent upgrade to the supported REST agent.

Method 1: Manual Workaround (No Upgrade Required)

1. Open the affected JOBS object.
2. Navigate to the Web Service > Response tab.
3. Under the Parse a Single Part Response section, locate the Output Name column.
4. Remove the ampersand (&) from the beginning of all entries (e.g., change &RESULT# to RESULT#).
   
   
5. Save the object. Note: In the newer, updated, IG REST agent, the ampersand is implied and should not be explicitly defined in this field.

Method 2: Permanent Fix (Agent Upgrade)

Upgrade the agent from the legacy RA REST solution to the Integration.REST (IG REST) agent (available for v21 and v24).

1. Download the Integration.REST agent files from the Broadcom Support portal.
2. Follow the standard upgrade instructions to start the new agent.
3. Automatic Conversion: Export your current jobs and re-import them; the import process will automatically strip the ampersands from the Output Name fields.
4. New objects created with the IG REST agent will no longer allow the & prefix in these fields, preventing the issue entirely.

Note: The legacy RA REST solution reaches End of Support on September 30, 2025. It is highly recommended to migrate to the Integration.REST agent as soon as possible.