Loading

Troubleshooting JBSystemFlow errors

Publiceringsdatum: Jun 10, 2025
Beskrivning
The JBSystemFlow Flow is created as a result of activating a Salesforce Data Entry Event in a Marketing Cloud Business Unit that is integrated with an Org using Marketing Cloud Connect. This flow runs when a record is Updated or Created on the Object that the Flow is assigned to, and has the potential to error just like any other Flow.
Lösning

Below are the most common reasons that a JBSystemFlow would fail:


CPU Limit:

The most common cause for a JBSystemFlow to error is when a single transaction exceeds its CPU Limit. Oftentimes, when a CPU Limit error is thrown, the culprit is not the JBSystemFlow itself. As our Flow usually runs late in the order of operations for a transaction, it's oftentimes other processes and Flows that take up a large amount of the CPU Limit, and then the JBSystemFlow takes up the last bit of CPU Limit. To troubleshoot, run Debug Logs when replicating the issue and look at the CPU usage of each portion of the log to see what is taking up the most CPU time.

In the instance that the JBSystemFlow is the culprit for a exceeding CPU Limit error, the two most likely causes are either too many records in a single Update/Create batch, causing the JBSystemFlow to have to run for every record evaluated, or for there to be too many decisions (Journeys) in a single JBSystemFlow, causing it to have to run really large Flows.

Too many SOQL Queries:

The JBSystemFlow runs for every record that is Updated or Created to see if it matches criteria for a Marketing Cloud Journey. The two most likely causes are either too many records in a single Update/Create batch, causing the JBSystemFlow to have to run for every record evaluated, or for there to be too many decisions (Journeys) in a single JBSystemFlow, causing it to have to run really large Flows.

Another problem could be another Process or Flow running most of the SOQL Queries, then the JBSystemFlow running to take the last bit. To troubleshoot, run Debug Logs when replicating the issue and look at the SOQL Usage of each portion of the log to see what Flow is using the majority of the SOQL Limits.
Knowledge-artikelnummer

000394130

 
Laddar
Salesforce Help | Article