Loading
Salesforce now sends email only from verified domains. Read More
Automate Your Business Processes
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          When Do Processes Evaluate Record Changes?

          When Do Processes Evaluate Record Changes?

          Processes start automatically and are invisible to the user. Before you design or activate a process, understand which changes trigger processes.

          Required Editions

          Important
          Important Where possible, we changed noninclusive terms to align with our company value of Equality. We maintained certain terms to avoid any effect on customer implementations.
          Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience
          Available in: Essentials, Professional, Enterprise, Performance, Unlimited, and Developer Editions
          Important
          Important Support and updates for Process Builder have ended as of December 31, 2025. This means that support won't be provided for any process and bugs in the Process Builder product won't be fixed. See Workflow Rules & Process Builder End of Support.

          After December 31, 2025, existing processes continue to run, and you can activate, deactivate, and edit them; however, we recommend using Flow Builder. To migrate existing processes, plan your switch to Flow Builder and use the Migrate to Flow tool. For new automations, create flows in Flow Builder.

          A record change can apply to more than just processes. When a record is created or edited, Salesforce evaluates whether to run other setup items, such as validation rules on the record. Salesforce evaluates the setup items in this order. For more information, see Triggers and Order of Execution in the Apex Developer Guide.

          • Validation rules
          • Assignment rules
          • Auto-response rules
          • Workflow rules and processes (and their immediate actions)
          • Escalation rules

          When you create a process, you associate the process with exactly one object. You also specify whether to evaluate only created records or both created and edited records. When you activate a process, it starts when a record change meets those settings.

          Processes evaluate record changes when:

          • A record is saved or created. Processes that are created after records are saved don’t evaluate those records retroactively.
          • A standard object in a master-detail relationship is reparented.
          • Users synchronize records that were changed while using Connect Offline.
          • If the lead setting Require Validation for Converted Leads is enabled, leads are converted.
          • Another process, workflow rule, or flow updates the record in the same save operation, if the process is configured to reevaluate records.

            Processes can reevaluate records up to five times in one save operation. In a batch update, processes reevaluate only changed records.

          Note
          Note A record change can trigger more than one process. You can’t determine which process starts first.

          Processes don’t evaluate record changes when:

          • Campaign statistic fields, such as individual campaign statistics or campaign hierarchy statistics, are updated.
          • Picklist values are mass replaced.
          • Address fields are mass updated.
          • Divisions are mass updated.
          • Territory assignments of accounts and opportunities are modified.
          • Self-Service Portal, Customer Portal, or partner portal users are deactivated.
          • State and country/territory data is converted with the Convert tool.
          • Values for state and country/territory picklists are modified using AddressSettings in the Metadata API.
           
          Loading
          Salesforce Help | Article