Loading

Process or Flow unknown_exception with a stacktrace of -548403183

Publiseringsdato: May 6, 2026
Beskrivelse

With Process Builder, using an action to update records which are related to the current record, depending on how you set your criteria, the Process might time out in getting the list of records. This can also happen when you use a Fast Lookup element in a Flow.

For example, a Process Builder on Lead records may be configured to update all related Activities where the criteria is set to "Closed Does not equal Boolean True". When multiple Leads are mass-updated from a list view, the Process runs a combined SOQL query for all activities across all selected Leads, which can cause a query timeout.

Løsning

The resulting timeout happens because the criteria is non-selective. For more information, refer to the Salesforce Engineering blog on query performance: Maximizing the Performance of Force.com SOQL, Reports, and List Views

Instead of using "Does Not Equal True", change the criteria to "Closed Equals Boolean False". This makes the SOQL query selective (uses an index), which prevents the timeout.

Why Non-Selective Queries Time Out

Non-selective queries scan a large number of records instead of using indexed fields, which increases execution time and can lead to timeouts—especially during bulk operations such as mass updates. By using selective filters (like equality conditions on indexed fields), Salesforce can retrieve records more efficiently and avoid performance issues.

Knowledge-artikkelnummer

000383910

 
Laster
Salesforce Help | Article