The OOB Flow Designer flows generated from the store application "Security Operations Spoke" can not be triggered successfully even if the SIR record that is created or updated matches the trigger conditions of the flowsDescriptionThe OOB Flow Designer flows generated from the store application "Security Operations Spoke" can not be triggered successfully even if the SIR record that is created or updated matches the trigger conditions of the flows. There is an issue with the initial activation of the flows. The flows are initially not active when the store application "Security Operations Spoke" is installed. After activating the flows, the flows do not trigger even with matching condition. The related sys_flow_record_trigger records for the flows are still set to Active=False, even after the flows are activated.Steps to Reproduce 1. Navigate to System Definition -> Plugins. Find and install the store application "Security Operations Spoke".2. Once the store application is installed, go to the Flow Designer. Find the following 2 flows which are triggered when a record is created or updated in the table "Security Incident" [sn_si_incident]:"Security Incident - Automated Malware Playbook - Template V1" (Trigger conditon: Category = "Malicious code activity")"Security Incident - Automated Phishing Playbook - Template V1" (Trigger conditon: Category = "Phishing" AND Source = "Email")3. Activate the 2 flows.4. Navigate to the table sn_si_incident, click "New" button to create a new SIR record with the following details:Category = "Malicious code activity"Short description = "test"5. Save or Submit the new SIR record.6. On the SIR record, click the related link "Show Response Tasks" or "Show All Related Lists". Notice that on the "Response Tasks" related list there is no response task created. The expected behavior is that there should be a response task created for this SIR record according to the design of the flow "Security Incident - Automated Malware Playbook - Template V1".7. Go to the "Executions" list in Flow Designer and notice that there is no flow execution found for the flow "Security Incident - Automated Malware Playbook - Template V1". Therefore, even if the SIR record matches the trigger condition of the flow, the flow is still not getting triggered.8. Navigate to the table sn_si_incident, click "New" button to create a new SIR record with the following details:Category = "Phishing"Source = "Email"Short description = "test"9. Repeat the step 5, 6 and 7. Notice that there is also no response task created for the SIR record according to the design of the flow "Security Incident - Automated Phishing Playbook - Template V1" as this flow is also not getting triggered even if the SIR record matches the trigger condition of the flow.WorkaroundThe workaround for this problem is to deactivate and re-activate the flows once again a second time so that the related sys_flow_record_trigger records should be now recompiled and set to Active=True. After the second activation, the flows should get triggered successfully when the trigger conditions match.Related Problem: PRB1500009