Notifications

86 views

Description

Flows get stuck Continue Sync (sys_flow_context.state) after a second REST step on the MID

Steps to Reproduce

Create an action "testAction" with the following steps:
1. Script 1 -> gs.print("hi");
2. Rest Action on MID
3. Script 2 -> gs.print("hi");

Publish the action
Create a flow "testFlow" and add the following

1. testAction
2. wait for time (10) seconds
3. testAction

Activate the flow
Goto Background Scripts and run the following:
sn_fd.FlowAPI.executeFlow("global.testFlow"); -> gets stuck in 'Continue Sync' state after 10+ seconds, open the execution and check 1st two actions in 'Complete State' 3rd step in no state

Alternatively:

sn_fd.FlowAPI.startFlow("global.testFlow"); -> check executions gets completed after 10+ seconds

Workaround

Use startFlow instead of executeFlow OR do not quiesce the flow. 

executeFlow is meant to return the flow outputs and the outputs won't be available if the flow quiesces.


Related Problem: PRB1417621

Seen In

SR - IRM - Audit Management - New York 2019 Q3
SR - IRM - GRC Profiles - Madrid 2019 Q2
SR - IRM - Policy and Compliance - Madrid 2019 Q2
SR - IRM - Risk Management - New York 2019 Q3
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 - Splunk Sighting Search Integration - Madrid 2019 Q1
SR - SIR - Store SecOps Setup Assistant - Madrid 2019 Q2
SR - SIR - Store Trusted Security Circles Client - New York 2019 Q3
SR - SIR - Threat intelligence - New York 2019 Q3
SR - VR - Qualys - New York 2019 Q3
SR - VR - Vulnerability Response - New York 2019 Q3
SR - VR - Vulnerability Response PA Content - Madrid 2019 Q2

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-09-17 19:30:13
Published:2020-08-03