117 views

Description

There's a possible race condition when the flow is being read by a MID server and an update to the flow happens on the instance.  This will cause the flow to error out.  Additionally, there's another possibility that an update could happen on the on the instance after the flow has been sent back from the MID.  Both scenarios can occur if the flow has an Ask For Approval with a group of approvers followed by an action that goes to the MID.  

Steps to Reproduce

1) Create a flow with a group approval with multiple members followed by an action that requires mid.
2) Ensure the serialized process plan will span multiple sys_json_chunk rows by adding some steps with very large inputs
3) Execute the flow and approve all the approvals simultaneously
4) Hopefully the race condition will occur where the mid reads a partial JSON document for the plan.

Workaround

The likelihood of the race condition occurring can be reduced by adding a "Wait for a duration of time" action between the group approval action(s) and action(s) that require mid.  The the longer the duration of the "Wait for a duration of time" action the more effective it will be.  30 seconds may be sufficient, but you'll want to test this thoroughly in your environment.

Another possible workaround, would be to put either the approval or the action that goes to the MID in to a subflow and call the subflow via dynamic flows.  As dynamic flows executes in a separate context this will isolate approval updates from MID execution.  Dynamic flows is available in Orlando and beyond.

https://docs.servicenow.com/bundle/orlando-servicenow-platform/page/administer/flow-designer/concept/flow-logic-dynamic-flow.html


Related Problem: PRB1410951

Seen In

SR - IRM - Audit Management - New York 2019 Q3
SR - IRM - GRC Profiles - Madrid 2019 Q2
SR - IRM - PA Premium Integration - New York 2019 Q3
SR - IRM - Policy and Compliance - Madrid 2019 Q2
SR - IRM - Risk Management - New York 2019 Q3
SR - IRM - Vendor Risk Management - Madrid 2019 Q1
SR - ITOM - Discovery and Service Mapping - v1.0.35
SR - Platform - Performance Analytics Content Pack for Guided Tours - v1.0.1
SR - Security - Integration Framework - Madrid 2019 Q2
SR - Security - Support Common - Madrid 2019 Q2
SR - Security - Support Orchestration - Madrid 2019 Q2
SR - SIR - Security Incident Response - Madrid 2019 Q2
SR - SIR - Security Incident Response PA Content - New York 2019 Q3
SR - SIR - Store SecOps Setup Assistant - Madrid 2019 Q2
SR - SIR - Store Threat Core - Madrid 2019 Q2
SR - SIR - Store Trusted Security Circles Client - New York 2019 Q3
SR - VR - Vulnerability Response - New York 2019 Q3

Intended Fix Version

Quebec

Fixed In

Orlando Patch 9
Paris Patch 3

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-11-19 22:45:53
Published:2020-10-02