Flows are not Triggering when the Condition is met Issue You have found that some or all of your Flows are no longer triggering even though the Condition is being met.CauseThis is most likely to be happening because the Flows have been moved by an Update Set which has not contained all the Trigger Mapping which is necessary for the Flows to run. To verify if this is the Root Cause please follow the below steps to check if the Trigger Mapping is set up correctly. Find the Flow Trigger Record: Get the Sys ID of the Flow [sys_hub_flow] which is not triggeringNow open the [sys_flow_trigger_plan] Table and Query for Plan ID = Flow Sys ID (From Step 1) https://<instance_name>.service-now.com/sys_flow_trigger_plan_list.do?sysparm_query=plan_id=<flow_sys_id> Open the Record which is QueriedUse Right Click Header > Show XML and Copy the Sys ID from inside the "trigger" Field of this RecordGo to the [sys_flow_trigger] Table and Query for Sys ID = Flow Trigger Sys ID (From Step 4) https://<instance_name>.service-now.com/sys_flow_trigger_list.do?sysparm_query=sys_id=<sys_flow_trigger_sys_id> Congratulations! You have now found the Flow Trigger Record for this Affected Flow.Now please follow the "How To Verify the Trigger Mapping" Steps to ensure that this Trigger is mapped correctly. Important Notes: If the [sys_flow_plan_context_binding] Record is missing then it most likely means that this Flow has never been executed.If the [sys_flow_trigger] Record is missing then this is the Root Cause for the Flow not being able to execute. [Please modify and republish the Flow to resolve this] How To Verify the Trigger Mapping: NOTE: Please be aware these steps will not work after the Tokyo Upgrade due to changes to the Table Structure for [sys_json_chunk]. Please Copy the Sys ID of the Trigger Record we identified in Step 6 of the earlier steps.Now open the [sys_trigger_runner_mapping] Table and Query for Trigger.Sys ID = Trigger Sys ID (From Step 1) https://<instance_name>.service-now.com/sys_trigger_runner_mapping_list.do?sysparm_query=trigger.sys_id=<sys_flow_trigger_sys_id> Next Copy the [sys_trigger_runner_mapping] Sys ID of the Record which you have found in Step 2Open the [sys_json_chunk] Table and Query for Parent = Trigger Runner Mapping Sys ID (From Step 3) https://<instance_name>.service-now.com/sys_json_chunk_list.do?sysparm_query=document_id=<sys_trigger_runner_mapping_sys_id> If you were able to find all the records using these Steps then the Trigger Mapping is set up correctly and there is another issue affecting the Flows.If you did not find all the records then it means the Trigger Mapping is incorrect and this is the Root Cause for why the Flow is not triggering. ResolutionTo resolve this issue we recommend you perform the following: Make a small modification to the Affected Flow (Such as a Comment Change)Publish and Activate the Flow This will force the Flow to recompile and the Triggers will now be generated correctly. Additionally we suggest to identify the Update Set which contains the Affected Flow and inform the Customer that this should not be used in the future.