Expected Data Limits with Flow?

[allisonletts]

Has this solution been tested at scale? How many records can it handle before max CPU time exceeded?

I'd like to use it for a cleanup process to avoid data skew, so I have thousands of records to move.

[jamessimone]

@allisonletts due to Flow only being able to update owners with invocable actions in an after update setting - which requires recursion - using Flow with the round robin assigner will be naturally more limited than using Apex (where recursion is not required).

[allisonletts]

@jamessimone order of magnitude, should it be able to handle more like 100, 1000, or 10000?

[jamessimone]

@allisonletts it depends on how much else you have going on in your Record Triggered flow. If the round robin assignment is the only thing happening before/after update, it should scale fairly well. For more complicated flows, I could definitely see some eventual timeouts - one way to handle this for Flow driven assignments would be to use the bulk API to upload updates (using a tool like dataloader) so that the chunk size for the updates could be set to something reasonable, like 200 records per chunk.