Workflows has a few limitations that should be considered when choosing this technology; here are some of the most relevant (as of winter 2020):

• Total inactive and active rules across objects (including workflows, assignment rules, auto-response and escalation rules): 2,000
• Total inactive and active rules per object: 500
• Active rules per object: 50
• Immediate actions per workflow: 40 (up to 10 for each action type)
• Time-based trigger per workflow: 10 (up to 10 for each action type)
• Time-based workflow execution per hour: 1,000
• Email alerts allocation per day: 1,000 alerts per standard license, up to 2 million

Before closing the chapter, let's list some considerations about adopting workflows on your business automations:

• When a custom object is deleted, workflow rules on that custom object are deleted as well.
• It is possible to run cross object field updates on accounts/opportunities when a lead is converted (use the Require Validation for Converted Leads on the Setup | Features Settings | Marketing | Lead Settings page).
• The order of the automated actions is not guaranteed, although field updates are always executed first.
• If you replace one or more workflow rules to replace an Apex trigger (or vice versa) remember to disable the trigger before activating the workflow rules; otherwise, both will be executed and you get unexpected automated behavior.
• Workflow rules are executed when a child standard or custom object with a master-detail field is re-parented.
• If the organization uses multiple languages, create a workflow using your own language (up to 25 filter criteria of 255 characters each), but remember that if you are using picklist filtering, the system uses the default value in the criteria, so you should use the values of the original language the workflow rule was created with when editing the rule (change the company default language accordingly).
• When using filter on record type labels, always use the master label and not the translated label; otherwise, the workflow won't trigger at all.
• A workflow rule doesn't fire if a condition has a reference to a field that doesn't have a value. For example, if a criteria is defined on the contact object where Account.Active__c == true, but the Contact.AccountId field is blank, the criteria is not matched and the workflow won't fire at all. In this situation use formula criteria to check whether the field is filled in or not.
• There are some actions on the Salesforce setup that don't trigger rules:
  • Replacing picklist values
  • Changing territory assignments on accounts and opportunities
  • Converting leads to person accounts
  • Deactivating self-service portal, customer portal, or partner portal users

This section helped us understand further the work considerations of workflows.