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.
Available in: Essentials,
Professional, Enterprise, Performance, Unlimited,
and Developer Editions
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.
API Name
Description
myVariable_current.field
field is the name of the field that’s referenced.
myVariable_current refers to the field values that the record
had when it started the process.
For example,
myVariable_current.Id corresponds to the record’s
field value for Id when the record started the process.
myVariable_old.field
field is the name of the field that’s referenced.
myVariable_old refers to the most recent previous values of
the record that started the process.
For example,
myVariable_old.Id corresponds to the record’s field
value for Id immediately before the record started the
process.
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 Error or warning messages can refer to a “flow” instead of a “process”. Those messages
still apply to your process.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.
