Intermittent 400 Bad Request after IG REST migration

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

REST Jobs are intermittently failing with a "400 Bad Request" error (Response family: CLIENT_ERROR) after migrating from the RA REST Agent to the IG REST Agent

The error messages falsely indicate that required fields are missing, or that a workflow trigger is not enabled. However, when these same jobs are restarted without any modifications to the job objects, they execute successfully

ERROR: Response error code: 400 (Response family:CLIENT_ERROR), Exception: {"stateMachineArn":["This field is required."],"input":["This field is required."]}:Bad Request

Environment

IG REST Agent 24.1

Cause

The problem occurs because of how the JSON data was being passed to the REST server. By passing the JSON payload as a string, some target REST APIs did not respond correctly. This behavior was unpredictable, as even the exact same REST API call behaved differently depending on the host.

Resolution

Integration REST Agent version 24.2.0 fixes that by changing the data transmission method. The JSON payload is now passed as a byte array instead of a string, which ensures target REST APIs respond correctly.

Please upgrade to that version or a later version.