Multiple record-triggered flows on the same object

Each time a record is created or updated, all record-change processes for its object are executed. Using only one record-triggered flow keeps the order of operations predictable and reduces the risk of hitting governor limits.