Back to LinkedIn posts

LinkedIn post 366

πŸ“ŠπŸš« Are your Salesforce Flows hitting the 2000-iteration limit(*)? πŸš«πŸ“Š

πŸ“ŠπŸš« Are your Salesforce Flows hitting the 2000-iteration limit(*)? πŸš«πŸ“Š

(*) only applicable to flows in API versions 56 and earlier

Farah Sherif Ghanem points out a reason to use Invocable Apex from Flows in her article.

😬 Flow Limitations: flows have a limit of 2000 executed elements at run time.

🚨NOTE🚨: The limit of 2000 element executions per flow at runtime was removed in API version 57. (Thanks, Chris V!)

So if your flow still is breaking, change its API version to 57 or higher.
πŸ”— https://lnkd.in/gD2HJuUX

Farah shows how processing just 600 records can push your flows to their iteration limits due to loop and assignment elements.

I've had a client with a screen flow that queried contacts related to accounts via the AccountContactRelation object to display the related contacts in a data table. The flow worked for the sheer majority of the accounts but there was a single account with hundreds of related contacts and it made the flow run into the issue. The error simply appeared via email as "Limit Exceeded You or your organization has exceeded the maximum limit for this feature."

πŸ”— Link to Farah's article:
https://www.linkedin.com/pulse/when-call-apex-action-from-flow-farah-sherif-ghanem/

πŸ“ŠπŸš« Are your Salesforce Flows hitting the 2000-iteration limit(*)? πŸš«πŸ“Š