---
schema_version: "1"
id: bae13695e71232f200a228e71ce31bfb41528bb2bd128ce3d41d2da2c5bf2e77
title: Errors in the Process Builder
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/process_troubleshoot_design.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.process_troubleshoot_design.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 2b467f5c94816fb1e3a599b942226e78e67c4a4e4503244f150b8f1e0ac673cc
description: The API names for criteria nodes and actions are created in the background. When you create or update processes, you can see error messages that reference those names to help you identify specifically where the problem occurred.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# Errors in the Process Builder

The API names for criteria nodes and actions are created in the background. When you create or update processes, you can see error messages that reference those names to help you identify specifically where the problem occurred.

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

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:36.76470588235294%">
          <col style="width:63.235294117647065%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d249586e114">API Name</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d249586e117">Description</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="API Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d249586e114 ">
              <samp>myVariable_current.<var>field</var></samp>
            </td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d249586e117 ">
              <p><var>field</var> is the name of the field that’s referenced.
                <samp>myVariable_current</samp> refers to the field values that the record
                had when it started the process.
              </p>
              <p style="margin-bottom:0;">For example,
                <samp>myVariable_current.Id</samp> corresponds to the record’s
                field value for <samp class="parmname">Id</samp> when the record started the process.
              </p>
            </td>

          </tr>
          <tr class="">
            <td data-label="API Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d249586e114 ">
              <samp>myVariable_old.<var>field</var></samp>
            </td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d249586e117 ">
              <p><var>field</var> is the name of the field that’s referenced.
                <samp>myVariable_old</samp> refers to the most recent previous values of
                the record that started the process.
              </p>
              <p style="margin-bottom:0;">For example,
                <samp>myVariable_old.Id</samp> corresponds to the record’s field
                value for <samp class="parmname">Id</samp> immediately before the record started the
                process.
              </p>
            </td>

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

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

Example

```
 The element has an invalid reference to “myVariable_current.AnnualRevenue”.
```

myVariable\_current.AnnualRevenue refers to the value for the field AnnualRevenue when the record started the process.

![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 Error or warning messages can refer to a “flow” instead of a “process”. Those messages still apply to your process.

#### See Also

- [Common Reasons Why Processes Fail](https://help.salesforce.com/s/articleView?id=platform.process_errors.htm&release=264.0.0&type=5 "Here are some common design problems that cause processes to fail.")