Avoid Creating Multiple Record-Change Processes for an Object
Where: This change applies to Lightning Experience and Salesforce Classic in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.
Why: We recommend restricting your org to one record-change process per object. The more record-change processes that are associated with an object, the more likely your org is to exceed limits, such as SOQL queries. In addition, if you create multiple record-change processes for an object, Salesforce can’t guarantee which process is evaluated first or second or seventh.
Whenever you see this list of processes in the Object node, consider adding to an existing process instead of creating another one. We recommend automating everything in one process per object, whenever possible.