I’m working with a Salesforce Flow that processes a relatively large number of records, and I’m looking for ways to improve its performance and reliability.
The Flow currently performs several record queries and updates during execution. As the amount of data increases
,the Flow takes longer to complete and can sometimes approach Salesforce governor limits.
What are some recommended approaches for optimizing a Flow in this situation? For example, would reducing Get Records operations, using collections more effectively, or moving some logic to Apex help?
I’d appreciate any practical suggestions or best practices for designing scalable Salesforce Flows.
#Salesforce Platform #*saleforce Platform Basic* - Understand The Salesforce Architecture #Flows #Slack Developers #Automation
Hi @James K.k
The biggest win is usually reducing database operations, not just reducing Flow elements.
I’d bulkify the Flow around collections, eliminate Get Records/DML inside loops, and query only the fields/records actually needed. If the volume or logic still pushes governor limits, I’d move that part to Apex and let Flow handle the orchestration.