When using the activity Run flow/subflow/action, the activity sometimes errors with the message: 'listenedTo Not Defined.'Issue When using the activity Run flow/subflow/action, the activity sometimes errors with the message: 'listenedTo Not Defined.' Release Zurich Patch 12 Cause The Run flow/subflow/action workflow activity waits for the launched flow to finish by listening for changes to the flow's state. When that notification is handled right away, the activity works as expected. When the workflow context is busy processing at the moment the flow completes, the platform saves the notification and replays it later. In that replay, the information the activity needs (the flow record that changed) isn't available. The activity then faults with "listenedTo" is not defined. Resolution As a workaround the lines 38-40 within the "Run flow/subflow/action" workflow activity definitionhttps://INSTANCE.service-now.com/nav_to.do?uri=wf_activity_definition.do?sys_id=1db36192c31002101fc9cde97640ddffNeed to be replaced by the following:onListener: function() {var flowContextGr = new GlideRecord('sys_flow_context');flowContextGr.get(activity.scratchpad.flowContextId);this.checkFlowContextState(flowContextGr);}