Loading

JBSystemFlow and JBSystemProcess CPU Usage After Summer '22 Release

Publiceringsdatum: Apr 17, 2026
Beskrivning

The Spring '21 Update Accurately Measure the CPU Time Consumption of Flows and Processes (Update) (please right-click the link and open in a new tab to see the release notes) was an optional update. The update is now being enforced from Summer '22 onward. After this update, you may see "CPU Time Limit Exceeded" errors coming from JBSystemFlow_{Object} or JBSystem_{Object}_Process. These flows/processes are components of the Marketing Cloud Connect feature Journey Builder Integration. Prior to this update being enabled, you would not see either of these components contribute to the "CPU time". The logs were inaccurately attributing CPU time to downstream actions, such as an Apex Trigger. 

Prior to Summer '22

14:12:51.320 (320074551)|FLOW_START_INTERVIEW_BEGIN|7462e418cb980516f32a495e287c1809ac4cbc8-4af2|JBSystem_Contact_Process
14:12:51.320 (320382621)|FLOW_START_INTERVIEW_LIMIT_USAGE|SOQL queries: 0 out of 100
14:12:51.320 (320397721)|FLOW_START_INTERVIEW_LIMIT_USAGE|SOQL query rows: 0 out of 50000
14:12:51.320 (320407214)|FLOW_START_INTERVIEW_LIMIT_USAGE|SOSL queries: 0 out of 20
14:12:51.320 (320416062)|FLOW_START_INTERVIEW_LIMIT_USAGE|DML statements: 0 out of 150
14:12:51.320 (320424289)|FLOW_START_INTERVIEW_LIMIT_USAGE|DML rows: 0 out of 10000
14:12:51.320 (320431874)|FLOW_START_INTERVIEW_LIMIT_USAGE|CPU time in ms: 0 out of 15000


After Summer '22

15:41:51.940 (940782672)|FLOW_START_INTERVIEW_BEGIN|4004deb004d1eea8663f251c601a1809ae647bf-63ba|JBSystem_Contact_Process
15:41:51.940 (941188117)|FLOW_START_INTERVIEW_LIMIT_USAGE|SOQL queries: 0 out of 100
15:41:51.940 (941205285)|FLOW_START_INTERVIEW_LIMIT_USAGE|SOQL query rows: 0 out of 50000
15:41:51.940 (941214222)|FLOW_START_INTERVIEW_LIMIT_USAGE|SOSL queries: 0 out of 20
15:41:51.940 (941227398)|FLOW_START_INTERVIEW_LIMIT_USAGE|DML statements: 0 out of 150
15:41:51.940 (941235166)|FLOW_START_INTERVIEW_LIMIT_USAGE|DML rows: 0 out of 10000
15:41:51.940 (941244858)|FLOW_START_INTERVIEW_LIMIT_USAGE|CPU time in ms: 305 out of 15000

Note that the CPU time is a non-zero number.
 

Lösning

The Salesforce Data Event creates flows in the connected Sales or Service account. The flows become larger/more complex as the number of journeys using the same object increases, the number of fields being selected increases, or the complexity of the filters grows. If you receive a notification for "CPU time limit exceeded", check for running journeys that your Marketing Cloud account has that use the same object, for example Contact. If there are any journeys that are "running" but not being used, stopping these journeys removes their reference within the flows for that object. This can help reduce CPU time. 

Outside of Journey Builder, reducing the batch size of any bulk updates can also reduce CPU time. If you batch import 200 records and hit this limit, try reducing to 100 and see if it is successful. Salesforce CPU limits are on a per transaction basis. The bigger the transaction, the more likely you will hit this limit. 

It is not possible to increase the CPU timeout.

Note: If you have an Enterprise 2.0 account with more than one Business Unit (BU) connected to the same Org, you may need to review each Business Unit. Each BU contributes to the same Flow if it uses the same object. 
 

References

Execution Governors and Limits
 

Knowledge-artikelnummer

000393143

 
Laddar
Salesforce Help | Article