---
schema_version: "1"
id: 8fce6a578124329fffdca730bed8c16f71611283feb6e53ee2ae04ba7bd4dad1
title: What Does This Approvals Error from a Classic Approval Process Mean?
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/approvals_troubleshoot.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.approvals_troubleshoot.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 93d9bfc95efff575df396c206b4ba233e511822ab8b0c37bb3e7bc5385520210
description: Here are some errors that you can come across when you submit a record for approval or respond to an approval request.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# What Does This Approvals Error from a Classic Approval Process Mean?

Here are some errors that you can come across when you submit a record for approval or respond to an approval request.

### 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 and Lightning Experience</td></tr><tr class="" id="approvals_troubleshoot__d4881e54"><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</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 Try [Flow Approval Processes](https://help.salesforce.com/s/articleView?id=platform.automate_automated_approvals.htm&release=264.0.0&type=5 "As your company grows, so does the complexity of your approvals, often requiring input from multiple people in different departments across different time zones. This complexity can mean that you spend more time waiting for each person to complete their review in the right order. Flow Approval Processes helps you coordinate multistep reviews that involve users, systems, and conditional paths."), a modern alternative to Classic Approval Processes. This new feature provides a more flexible, user-friendly flow-based interface, and it can trigger on record changes, supporting Apex extensibility and detailed logging for compliance and audit trails. It supports dynamic routing based on data and business rules, unlike Classic Approval Processes, which are tied to specific objects and offer limited support for processes by using conditions. With Flow Approval Processes, you can monitor submitted records and quickly identify bottlenecks, giving you unprecedented visibility into approval workflows. And, like Classic Approval Processes, Flow Approval Processes don’t consume automation credits or orchestration runs.

## Manager undefined

## This approval request requires the next approver to be determined by the Field Name field.

## This value is empty.

Salesforce tried to route the approval request based on a hierarchical field, such as Manager. However, the field has no value or specifies an inactive user. This error can occur when someone submits a record for approval or when an approver responds to an approval request.

## Required fields are missing: \[FieldName\].

The classic approval process includes a field update that fails standard validation rules for the identified field. This error can occur even if the field isn’t visible on your page layout.

![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 Salesforce doesn’t check whether field updates pass _custom_ validation rules on fields.

## Entity "FieldName" not found.

An approval process associated with a deleted or deprecated object can remain in Salesforce. When Salesforce loads approval process metadata, the orphaned approval process prevents classic approval process metadata from loading. This includes approval processes for unrelated objects. To remove the orphaned approval process, contact Salesforce Customer Support.

#### See Also

- [Troubleshoot Email Responses to Approval Requests from Classic Approval Processes](https://help.salesforce.com/s/articleView?id=platform.approvals_processing_approval_requests_email_debug.htm&release=264.0.0&type=5 "When email responses aren’t working correctly, review these common issues.")
- [Approval Requests from Classic Approval Processes for Users](https://help.salesforce.com/s/articleView?id=platform.approvals_users.htm&release=264.0.0&type=5 "Your admin can set up classic approval processes that let you and other users submit records for approval, which results in approval requests.")