Avoid Unwanted Actions in Processes

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.

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 Check out this short video Avoid Unwanted Actions in Your Process to learn more about this option.

This setting isn’t supported if:

• 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.