---
schema_version: "1"
id: b8a671f8295da5f23de6fcf33c485b64f45a7d7364c2dac76eabb425acf4b07a
title: When Do Processes Evaluate Record Changes?
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/process_considerations_works.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.process_considerations_works.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 390886cc0d70239a34c511e5a2b09f2d1b7f61a37f9d2527752f312a9ab6fdfb
description: Processes start automatically and are invisible to the user. Before you design or activate a process, understand which changes trigger processes.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# 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](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_important.png)

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.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic (<a href="https://help.salesforce.com/s/articleView?id=xcloud.overview_edition_lex_only.htm&amp;language=en_US" target="_blank">not available in all orgs</a>) and Lightning Experience</td></tr><tr class="" id="process_considerations_works__d5720e343"><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <span id="process_considerations_works__d5720e347"><a name="process_considerations_works__d5720e347"></a><strong>Essentials</strong>, <strong>Professional</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</span></td></tr></tbody></table>

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_important.png)

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](https://help.salesforce.com/s/articleView?id=001096524&type=1&language=en_US).

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](https://help.salesforce.com/s/articleView?id=platform.flow_migrate_to_flow_learning_map.htm&release=264.0.0&type=5 "Flow Builder combines the capabilities of workflow rules and Process Builder in a single point-and-click tool, making it easier to create a triggered process. If you created triggered processes with workflow rules or Process Builder, use the Migrate to Flow tool to move them to Flow Builder. Start by migrating and testing in a sandbox environment before moving your new flows to production.") and use the [Migrate to Flow](https://help.salesforce.com/s/articleView?id=platform.flow_migrate_to_flow.htm&release=264.0.0&type=5 "Use the Migrate to Flow tool to convert your Process Builder processes and workflow rules into Flow Builder, including scheduled actions. The tool also supports partial migration of processes for most actions.") tool. For new automations, create flows in [Flow Builder](https://help.salesforce.com/s/articleView?id=platform.flow.htm&release=264.0.0&type=5 "Automation reduces repetitive work and helps your team complete tasks faster and more accurately. With Flow Builder, you can build simple or complex automations, forms, and guided experiences with no code. You can add forms to Salesforce pages and Experience sites, and launch flows using buttons, record triggers, or schedules.").

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](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_note.png)

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.