I'm working on a Flow that needs to update a large batch of related records (a few thousand) triggered from a record update on the parent object. I've read that Record-Triggered Flows can run into governor limits or performance issues at scale, and I'm trying to figure out the right pattern before I build this out further.
For those who've dealt with bulk updates like this — is it better to handle this with a Scheduled Flow / batch approach instead of a real-time Record-Triggered Flow, or is there a cleaner declarative pattern I'm missing? Trying to avoid needing an Apex trigger if possible, but open to it if that's genuinely the better path here.
The limit for number of records to be updated before hitting a limit is 10k across all DML statements (see documentation) so you should be able to use an assignment and a collection variable to update the value(s) needed and then do the update DML on the collection without an issue based solely on what is described here. I personally don't like scheduled flows as I've encountered some unexpected/unexplained behavior with them. Hope this helps!
