Flow Not Triggering Despite Matching Conditions in 'DevOps Risk Change Policy Flow'Issue The 'DevOps Risk Change Policy Flow' is not triggering even though the defined conditions appear to be met. Expected Trigger Conditions: Category is DevOpsType is NormalTemplate is not 'ASAP SQL Patching' However, the flow is not activating as expected under these criteria. Steps to Reproduce: Access the instance: volvoitsmdev2Review the flow 'DevOps Risk Change Policy Flow' and examine the configured trigger conditionsReleaseAllCauseThe flow did not account for scenarios where the Template field is empty. As a result, valid change requests without a defined template were excluded from triggering the flow.ResolutionTo resolve this issue, update the trigger conditions to account for empty template values: Modify the flow trigger to include: OR – Template is emptyTest the change in a sub-production (sub-prod) environment before promoting it to productionReview the flow’s behavior and reach out to support if any issues or questions arise