---
schema_version: "1"
id: f9a6a0e3de47ffef196efa0942f49f6b7436000c646306f947830dcdc5274c48
title: Avoid Unwanted Actions in Processes
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/process_advanced_previously_met.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.process_advanced_previously_met.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 49f40a23bd03b4455a18a00eb28e8193a0efad80651f0323c1f0408df1a5a8a9
description: When you add criteria to your process, you can choose to execute actions when specified criteria change.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# Avoid Unwanted Actions in Processes

When you add criteria to your process, you can choose to execute actions when specified criteria change.

### Required Editions

<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_advanced_previously_met__d2735e343"><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <span id="process_advanced_previously_met__d2735e347"><a name="process_advanced_previously_met__d2735e347"></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.").

For example, your process sends an email alert whenever a case has an Escalated status. Let’s say your support team repeatedly updates the case description with new information. Whenever the case is saved with a new description, your process can check specifically whether the Escalated status changed, rather than repeatedly sending email alerts. This way, the process executes actions only if the status was changed to Escalated during the latest update.

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

Tip Check out this short video ![Watch Video Demo](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/resources-global/_corporate/images/play_btn.png) [Avoid Unwanted Actions in Your Process](https://salesforce.vidyard.com/watch/1sbznRSzxtxhzRi3Hn_9ag) to learn more about this option.

This setting isn’t supported if:

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:10.666666666666668%">
          <col style="width:44.66666666666667%">
          <col style="width:44.66666666666667%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d52574e133">If Yes is...</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d52574e136">Actions are executed if...</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d52574e139">Actions are not executed if...</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="If Yes is..." class="slds-cell-wrap" style="vertical-align:top;" headers="d52574e133 ">Selected</td>

            <td data-label="Actions are executed if..." class="slds-cell-wrap" style="vertical-align:top;" headers="d52574e136 ">
              <ul>
                <li>The record was created.</li>

                <li>The record was updated. Its current values meet the conditions, and its most
                  recent previous values did not meet the conditions.</li>

              </ul>
            </td>

            <td data-label="Actions are not executed if..." class="slds-cell-wrap" style="vertical-align:top;" headers="d52574e139 ">
              <ul>
                <li>The record’s current values meet the conditions, and the record’s most recent
                  previous values met the criteria.</li>

                <li>The record’s current values don’t meet the conditions.</li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="If Yes is..." class="slds-cell-wrap" style="vertical-align:top;" headers="d52574e133 ">Deselected</td>

            <td data-label="Actions are executed if..." class="slds-cell-wrap" style="vertical-align:top;" headers="d52574e136 ">
              <ul>
                <li>The record was created.</li>

                <li>The record was updated, and its current values meet the conditions.</li>

              </ul>
            </td>

            <td data-label="Actions are not executed if..." class="slds-cell-wrap" style="vertical-align:top;" headers="d52574e139 ">The record’s current values don’t meet the conditions.</td>

          </tr>
        </tbody>
      </table>

- Your process starts only when a record is created.
- Your process starts when a record is created or edited and the criteria node doesn’t evaluate any criteria.
- The criteria node evaluates a formula, but the formula doesn’t include a reference to the record that started the process.
- Your process uses the Is changed operator in a filter condition.

#### See Also

- [Process Builder Advanced Option Considerations](https://help.salesforce.com/s/articleView?id=platform.process_advanced_considerations.htm&release=264.0.0&type=5 "Keep these considerations in mind when choosing advanced options.")