Troubleshooting Approval Processes and Record Locking

1. Why This Topic Matters
Approval processes are among the most business-critical automations an administrator owns. When a deal, discount, expense, or contract gets stuck in approval, revenue and operations stall, and the admin is the first person called. The Advanced Administrator exam (Advanced Process Automation section) tests whether you can diagnose why an approval request fails to submit, route, or complete, and whether you understand the side effect that confuses users most: record locking. Expect scenario-based questions such as 'A user receives an error that the record is locked' or 'The approval request was never assigned to an approver.' You must identify the root cause and the most appropriate fix, not just any fix.

2. What an Approval Process Is
An approval process is a declarative automation that routes a record to one or more users (approvers) for approval or rejection. Its building blocks are:
• Entry criteria – formula or field-based conditions a record must meet to enter the process.
• Approver selection – manager hierarchy field (Manager or a custom hierarchical user field), named users, queues, or the submitter chooses.
• Record editability – who may edit a record while it is pending: Administrators ONLY or Administrators OR the currently assigned approver.
• Approval steps – each with step criteria, approver assignment, approve/reject behavior (unanimous vs. first response for parallel approvers), and rejection behavior (final rejection or go back one step).
• Actions – Initial Submission, Approval Step (approve/reject), Final Approval, Final Rejection, and Recall actions. Available action types: Email Alert, Field Update, Task, Outbound Message. The system automatically adds a record lock on initial submission and a record unlock on final approval/rejection/recall (these can be changed to lock or unlock as needed).
• Approval History related list and the Approval Requests / Items to Approve list for monitoring.
• Settings: Allow submitters to recall, Email approval response (org-wide Process Automation Settings), Delegated approver per user, and 'Enable record locking and unlocking in Apex.'

3. How Record Locking Works
When a record is submitted, Salesforce locks it. A locked record:
• Cannot be edited by regular users through the UI, API, Data Loader, or most automation running in their context. Attempts return the error ENTITY_IS_LOCKED or 'This record is locked. If you need to edit it, contact your administrator.'
• Can be edited by users with the Modify All Data permission (system administrators) regardless of the editability setting.
• Can be edited by the currently assigned approver if the process is set to 'Administrators OR the currently assigned approver can edit records during the approval process.'
• Can be modified by Field Updates defined as approval actions (they run in system context as part of the process).
• Is unlocked automatically on final approval, final rejection, or recall (unless the admin changed the default unlock action to keep it locked).
• Locking the parent does not automatically lock child records; it only prevents reparenting changes that would modify the locked record's lookup fields from the locked side. Related records remain editable unless they are themselves locked.
• Apex can lock/unlock records using Approval.lock() and Approval.unlock() only if 'Enable record locking and unlocking in Apex' is turned on in Process Automation Settings. A Flow can call an invocable Apex action to unlock, or a Flow can use the Submit for Approval core action to start a process.
• A record can be in only one approval process at a time. Multiple active approval processes on an object are evaluated in the order you define; the first whose entry criteria match is used.

4. Systematic Troubleshooting Approach
Step A – Reproduce and read the exact error. Different messages point to different causes.
Step B – Check the Approval History related list (add it to the page layout if missing) to see status, assigned approver, comments, and whether the request is Pending, Approved, Rejected, or Recalled.
Step C – Review the approval process definition (Setup > Approval Processes > View Diagram) for entry criteria, step criteria, approver assignment, and actions.
Step D – Check users: Is the approver active? Is the Manager field populated? Is a delegated approver set and is the step configured to allow delegates?
Step E – Check settings: process active? editability setting? recall allowed? email approval response enabled?
Step F – Use debug logs and Setup Audit Trail when automation (Flow, Apex, integration) interacts with locked records.

5. Common Problems, Causes, and Fixes
Problem: 'Unable to submit for approval' / 'This record does not meet the entry criteria.'
Causes: entry criteria not met; approval process inactive; no process on that object; record already in an active approval. Fix: adjust criteria or data; activate the process; check Approval History for a pending request.

Problem: 'No applicable approval process found' or 'Manager undefined.'
Cause: approver is assigned via the Manager (or custom hierarchy) field and that field is blank on the submitter or record owner. Fix: populate the Manager field; or configure the step to use a specific user/queue; or allow the submitter to choose. Pay attention to the setting 'Use Approver Field of Record Owner' vs. the default which uses the submitter's field.

Problem: Approval request is stuck; approver never responds or has left the company.
Causes: approver inactive; approver lacks access; no delegate. Fix: an admin (Modify All Data) can approve, reject, or reassign the request from Approval History or the Approval Requests page; set a Delegated Approver on the user and check 'The approver's delegate may also approve this request' on the step. Note: inactive users should be removed/replaced as approvers; Salesforce prevents assignment to inactive users at submission time.

Problem: Approver cannot see Approve/Reject buttons.
Causes: not the current approver; parallel step requiring other approvers; delegate not permitted on that step; approver lacks read access to the record (approvers need at least Read access). Fix accordingly; admins can always act.

Problem: User gets 'record is locked' when editing.
Cause: expected behavior of record locking. Fixes (choose based on scenario): change editability to 'Administrators OR the currently assigned approver'; have the approver edit; have the submitter recall (if allowed), edit, and resubmit; admin edits; unlock via Apex/Flow invocable action. The exam often expects the least-privilege, declarative fix—usually changing the editability setting or using recall—rather than giving users Modify All Data.

Problem: Integration or Data Loader fails with ENTITY_IS_LOCKED.
Cause: the integration user lacks Modify All Data and records are pending approval. Fix: grant the integration user Modify All Data (if appropriate), exclude pending records, or unlock via Apex with record locking in Apex enabled.

Problem: Flow or trigger fails updating a record in approval.
Cause: same locking rule; automation running in user context is blocked. Fix: perform the update through an approval Field Update action, use Approval.unlock() in Apex, or redesign so the update happens before submission or after final approval.

Problem: Email approval responses are ignored.
Causes: 'Enable email approval response' not turned on in Process Automation Settings; approver replied from an email not matching their user record; wrong keyword. Fix: enable the setting; reply from the registered email with APPROVE/APPROVED/YES or REJECT/REJECTED/NO as the first line, optionally followed by comments.

Problem: Cannot edit or reorder the approval process.
Cause: once activated, you cannot add or remove steps or change certain attributes on a process that has records in it. Fix: deactivate (existing pending requests still complete), clone the process, modify the clone, and activate it; or wait for pending records to finish.

Problem: Final approval field update did not fire a Flow or trigger as expected.
Cause: approval Field Updates run in system context; record-triggered Flows do fire on them, but recursive save behavior and order of execution apply. Check 'Re-evaluate Workflow Rules after Field Change' on legacy field updates and verify Flow entry conditions.

Problem: Rejection sends the record back to the wrong place.
Cause: rejection behavior set to 'Go back 1 step' vs. 'Perform all rejection actions for this step AND all final rejection actions (Final Rejection).' Fix: edit step rejection behavior.

Problem: Users cannot recall a submission.
Cause: 'Allow submitters to recall approval requests' unchecked. Fix: enable on the process; admins can always recall.

6. Key Facts to Memorize
• Default lock on submission; default unlock on final approve/reject/recall.
• Modify All Data users can always edit, approve, reject, reassign, and recall.
• Editability choice: Administrators ONLY vs. Administrators OR currently assigned approver.
• Approval actions: Email Alert, Field Update, Task, Outbound Message (no direct Flow action inside approval actions; Flows are invoked indirectly or from Flow via Submit for Approval).
• One active approval process per record at a time; processes evaluated in order.
• Approval.lock/unlock requires 'Enable record locking and unlocking in Apex.'
• Delegated approvers must be enabled per step; delegates cannot reassign.
• Approvers need Read access to the record; queue approvers work only for objects that support queues.
• Approval History related list is the primary diagnostic view; Items to Approve / Approval Requests page lists pending work.
• Email approval response is an org-wide setting and matches the sender's email to the user record.

7. Exam Tips: Answering Questions on Troubleshooting Approval Processes and Record Locking
• Read for the error text. 'Record is locked' points to locking/editability; 'no approver' or 'manager undefined' points to approver assignment; 'does not meet entry criteria' points to criteria or inactive process.
• Identify who the user is. If the question says 'a system administrator', locking is not the barrier. If it says 'a sales rep' or 'integration user', locking almost certainly is.
• Prefer declarative, least-privilege fixes. Changing the editability setting, enabling recall, or reassigning the request beats granting Modify All Data to end users. Only choose Apex (Approval.unlock) when the scenario explicitly involves automation or integrations needing to update locked records.
• Know what admins can do. Questions about a stuck request with an unavailable approver usually have the answer 'an administrator reassigns the approval request' or 'configure a delegated approver.'
• Watch for the 'currently assigned approver' wording. That phrase is the exact editability option name; if an approver needs to edit the record before approving, that setting is the answer.
• Remember Approval History is a related list that must be on the page layout to be visible—missing history is a layout problem, not a process problem.
• Email responses: the fix is almost always 'enable email approval response' and 'reply from the email address on the user record.'
• Cannot modify an active process: the correct answer involves cloning, deactivating, or waiting for pending records—not deleting it.
• Eliminate distractors that mention Process Builder or Workflow Rules as the primary fix; current exams favor Flow and approval process configuration.
• Think through the lifecycle: submit (lock) → step actions → final approve/reject (unlock). Ask where in this lifecycle the described failure occurs, and pick the component that governs that stage.
• Parallel approvers: if 'all approvers must approve' is required, the step must be unanimous; if any one is enough, choose first response. Misconfigured step behavior is a frequent 'why did it approve early?' question.

8. Quick Scenario Practice
Scenario: A sales manager approving a discount must correct the discount percentage before approving but gets a locked record error. Answer: Set record editability to 'Administrators OR the currently assigned approver can edit records during the approval process.'
Scenario: A nightly integration fails for some Opportunities with ENTITY_IS_LOCKED. Answer: Records are pending approval; either grant the integration user Modify All Data, filter out pending records, or unlock via Apex with Apex locking enabled.
Scenario: Submissions fail for one department only. Answer: Those users' Manager field is blank or their manager is inactive; populate/replace the Manager.
Scenario: An approver on vacation has requests piling up. Answer: Assign a delegated approver on the user record and ensure steps allow delegate approval, or have an admin reassign.

Master these mechanics and you will be able to diagnose approval and locking issues quickly both on the exam and in real orgs.