Abnormal behavior with Workflow Manager Server on High-Availability Deployment

Question

We setup a Workflow Manager Server High-availability deployment. There are 2 Workflow Manager Server instances installed on 2 hosting ArcGIS Server machines.

Listing down the key issues noticed:

* While creating workflow jobs, job name indexes are not getting generated in sequence
* Workflow steps behavior is not consistent (abnormal) e.g. unexpected/unwanted dropdowns are being shown for steps
* When initiated multiple jobs, each job halted at different step
* Workflow performance is poor

Our environment has multiple network interface controller (NIC) cards or DNS entries, and we already followed the Configure ArcGIS Server in advanced scenarios documentation to handle it.

Environment:

* Portal for ArcGIS 10.9.1
* ArcGIS Server 10.9.1
* ArcGIS Workflow Manager Server 10.9.1
* ArcGIS Data Store 10.9.1

wfm_abnormal.png

Dense settings .JPG

abureaux_0-1724949250365.png

Ranga_Tolapi · Answer

hmmm... we are not alone here 😜

A defect bug is logged by Esri for the inconsistency that has been observed with the Job ID creation in the HA workflow manager. Details of the bug is as follow:

* Defect: BUG-000155792   
* Synopsis: Workflow Manager jobs not working in High Available site.  
* Status: In Review

EvaTTA · Answer

Just adding onto my experience with Ranga's point 2 observation on workflow steps having unwanted/unexpected drop downs. While my Workflow Manager Server is not HA, it is federated to a HA Portal and Enterprise. I would also like to know the cause of why a step that has not been configured to run in parallel (i.e., only having 1 path in and 1 path out) would result in the unwanted/unexpected drop downs.