I've been stress-testing the new Salesforce automation limits that rolled out last week, specifically around Process Builder and Flow. While I understand the need for governance, some of these changes feel like they'll force a major architectural rethink for complex integrations.
For example, the per-transaction limit on executed elements in a single flow is now 2,000. That might sound like a lot, but when you're syncing large data sets between Salesforce and Marketo using a triggered flow, you can hit that ceiling faster than you'd think. I had a flow that handled lead scoring updates and field sync—it started failing silently once the lead batch size exceeded a certain point.
Has anyone else run into this yet? I'm particularly curious about:
- Practical workarounds you've found for batch operations. Are we all moving to scheduled flows or external middleware for heavy lifting?
- How this impacts your existing Zapier or Workato integrations that rely on Salesforce triggers. Are you seeing more timeouts?
- Whether you're reconsidering which automation tool to use within Salesforce now (e.g., shifting logic to Apex for more control).
Here's a snippet of the kind of logic I had to refactor. The old process, which worked fine, was doing this for each record in a batch:
```xml
RecordCount
0
```
Now, I'm breaking it into multiple, smaller flows with explicit batch counters. It's more pieces to manage, but it stays under the limit.