scheduled job titled "Update journey progress with count for overdue tasks" is creating many flow contexts - Known Error

scheduled job titled "Update journey progress with count for overdue tasks" is creating many flow contexts Description There are lot of flow context records present for OOB "Compute journey progress" subflow. Upon checking the source, we could confirm that the major part is coming from the OOB scheduled job "Update journey progress with count for overdue tasks". This is causing the slowness issue as the schedulers are getting occupied due to high volume of this subflow execution records.

See KB1179826: Troubleshooting slow or queued flows

Steps to Reproduce

1. Go to the "Compute journey progress" subflow executions. 2. Notice that there are many executions and the major source is OOB scheduled job "Update journey progress with count for overdue tasks".

Workaround Reduce the frequency of the scheduled job: "Update journey progress with count for overdue tasks"

Edit "Update journey progress with count for overdue tasks" script with the code below to cancel queued flow contexts

// Pre-clean: cancel any QUEUED contexts for this flow to prevent duplicate/backlogged runs before recomputing all journeys (Global helper; running contexts untouched). try { var grFlowContext = new GlideRecord('sys_flow_context'); grFlowContext.addQuery('flow', '2bedb2f7772701103bc3bbdbef5a995f'); // Compute journey progress subflow grFlowContext.addQuery('state', 'QUEUED'); grFlowContext.query();

while (grFlowContext.next()) { sn_fd.FlowAPI.cancel(grFlowContext.getUniqueValue(), 'Compute journey progress subflow: Canceling backlogged queued contexts'); } } catch (e) { gs.warn('Error while canceling backlogged queued contexts for Compute journey progress subflow: ' + e); }

jny_JourneyProgressUtils.updateAllActiveJourneyProgress(); Related Problem: PRB1933371