Yielding to high priority flows feature has a couple of issues. - Known Error

Yielding to high priority flows feature has a couple of issues. Description Flow execution failed due to

SEVERE *** ERROR *** "Failed to iterate on data stream: Cannot invoke "com.snc.process_flow.val.ValMap.entrySet()" because "inputs" is null". Steps to Reproduce

Issue 1: com.glide.hub.flow.pause_low_priority_flows_enabled set to false is pausing the flows. so property is not honoured.

Issue 2: There is a mismatch in executing the steps. Next Step execution is started before the current step execution is completed.

Workaround This problem is currently under review and targeted to be fixed in a future release. Subscribe to this Known Error article to receive notifications when more information will be available

As a workaround please add the following three properties on your instance.

This property values are disabling the pausing of lower priority (MEDIUM or LOW) due to higher priority flow executions (HIGH): com.glide.hub.flow.pause_low_priority_flows_after_ms to 3000000 com.glide.hub.flow.pause_low_priority_flows_enabled = false com.glide.hub.threshold_of_high_priority_to_pause_low_priority = 1000000

So you will not see any flows being paused due to priority.

The impact of this workaround is if there are longer running flows it may take longer for high priority flows to start.