Databricks job fails with No enum constant if queued maximum concurrent runs set to 1

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

Within Databricks if a job has a "maximum concurrent runs" limit and option "Queue" set in Advanced settings it goes to queued status.

This works similarly than the max parallel executions in Automic.

But if we launch this job with Automic Integration Agent Databricks, the automic databricks job fails with the following error in the report:

ERROR: Possible Reason: Monitoring failed.
Error: No enum constant com.automic.agent.azure.databricks.util.RunJobStatus.QUEUED

Environment

Integration Databricks 21.1.3 and inferior

Cause

DE172331

Resolution

Update to a fix version listed below or a newer version if available.

Fix version:
Component(s): Agent Integration Databricks
Integration.Databricks 21.1.4 - Available

Additional Information

Latest available of Integration Databricks available here.