You are here:
Common Reasons Why Processes Fail
Here are some common design problems that cause processes to fail.
Required Editions
| Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience |
| 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.
- A user creates or edits a person account. An Account-based process evaluates the record. The process’s criteria node references an account field, for example, [Account].Name Equals Acme.
- The process references a field that hasn’t been set. For example, you reference
[Contact].Account.Description in your process. If the Account
lookup field isn’t set on the contact, the process fails because it doesn’t know which
account to reference.
The workarounds for this issue depend on where the reference exists in the process.
- If you reference it in filter conditions, add another filter condition that checks whether the lookup field is set. You can do the same workaround if it’s referenced in a formula, for example, [Contact].AccountId Is null False.
- Otherwise, consider making the fields required.
Did this article solve your issue?
Let us know so we can improve!
