Flows not triggered when using gs.eventQueue APIIssue Flows are not triggered when an event is created using the gs.eventQueue() API. When setting a flow trigger condition for event creation or update on the sysevent table, events created using the gs.eventQueue() method do not start the flow as expected. This is because gs.eventQueue sets setWorkflow to false, which prevents Flow Designer flows on the sysevent table from being triggered. Release Paris Cause In Paris, a fix was applied so that the trigger engine respects setWorkflow(false). As a result, Flow Designer flows do not run when setWorkflow is set to false. The gs.eventQueue() method sets setWorkflow to false by default, which causes flows triggered by record create or update events on the sysevent table to not start as expected. Resolution To restore the previous behaviour, create a system property to configure the trigger engine to ignore the setWorkflow(false) flag. Note: Enabling sysevents to trigger flows may have unintended instance-wide effects. Review the impact before enabling this property in production. Navigate to the system property creation page in your instance. Create a new system property with the following values: - Name: trigger_engine.ignore.set_workflow - Value: true 3. Save the record. Added context from ServiceNow docs: Once this system property is set to true, it overrides the default behaviour and allows Record triggers for Create, Create/Update, and Updated events on the sysevent table to trigger flows. Related Links Creating an event to trigger flow is not working Trigger flows when using the gs.eventQueue() method