Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
DictionaryRRecall Actions
AutomationIntermediate

Recall Actions

In Salesforce approval processes, the automated actions that execute when an approval request is recalled (withdrawn) by the submitter, such as field updates to revert the status or email notifications.

§ 01

Definition

In Salesforce approval processes, the automated actions that execute when an approval request is recalled (withdrawn) by the submitter, such as field updates to revert the status or email notifications.

§ 02

In plain English

👋 Study buddy

Recall Actions in Salesforce approval processes are automated actions that fire when someone withdraws an approval request they submitted. Actions might include field updates to revert status or email notifications letting approvers know the request was recalled.

§ 03

Worked example

scenario · real-world use

An employee at Larkmoor Capital submits an expense report for $4,200, then realizes within 5 minutes that he submitted the wrong receipts. He recalls the approval request before his manager has acted. Recall Actions fire automatically: a Field Update reverts ApprovalStatus__c to "Draft," an Email Alert notifies the manager that the request was withdrawn, a record is logged in the audit trail. The employee can revise and resubmit. Without Recall Actions, recalling would leave the record's status field stale; with them, the platform handles cleanup automatically.

§ 04

Why Recall Actions matters

In Salesforce approval processes, Recall Actions are the automated actions that execute when an approval request is recalled (withdrawn) by the submitter, such as field updates to revert the status or email notifications. Recall happens when the submitter realizes they need to change something or no longer need the approval, and recall actions handle the cleanup of any changes that were made when the request was submitted.

Recall actions are part of the approval process configuration. When you design approval processes, you configure what should happen on submission (initial actions), at each approval step, on final approval, on final rejection, and on recall. Thoughtful recall action design ensures that recalled requests are handled cleanly, with any submission-time changes reverted so the record is back to where it was before submission.

§ 05

How to set up Recall Actions

Recall Actions are the automated actions that fire when a submitter recalls their own approval request — typically reverting a Status field, unlocking the record, sending a notification. Less common than Initial Submission / Final Approval / Final Rejection actions because most orgs don't allow recall, but important when they do.

  1. Open Setup → Approval Processes → click into the relevant process

    Recall Actions are configured per Approval Process.

  2. Confirm Allow Submitters to Recall is ticked

    On the Approval Process detail page. Without this, submitters can't recall — Recall Actions never fire.

  3. Scroll to Recall Actions section

    Below Final Rejection Actions.

  4. Click Add New → pick Action Type

    Field Update / Email Alert / Task / Outbound Message. Field Update commonly reverts Status to Draft.

  5. Configure the Field Update

    Pick field, new value ("Status = Draft"). Make sure to also Unlock the record — otherwise recalled records stay locked.

  6. Save the action

    Action runs when submitter clicks Recall. Test in a sandbox by submitting and recalling a sample record.

Key options
Allow Submitters to Recallremember

Master toggle. Required for Recall Actions to fire.

Action Typeremember

Field Update / Email Alert / Task / Outbound Message.

Unlock the recordremember

Critical — otherwise recalled records stay locked.

Gotchas
  • Recall Actions only fire if Allow Submitters to Recall is ON. Many orgs leave it OFF, making Recall Actions config dead code.
  • Forgetting to unlock the record on recall leaves recalled records LOCKED — same issue as Final Rejection Actions. Always include an Unlock action.
  • Recall is submitter-initiated, not approver-initiated. Approvers can't unilaterally recall a request — they can only approve / reject. Build a separate process if you need approver-initiated cancellation.
§ 06

How organizations use Recall Actions

NovaScale

Configures recall actions to revert field updates that happened on submission, keeping records clean after recalls.

Cobalt Ventures

Uses recall email notifications to inform approvers when requests are withdrawn before they have to act.

BrightEdge Solutions

Treats recall action design as part of complete approval process configuration.

§

Trust & references

Official documentation

Straight from the source - Salesforce's reference material on Recall Actions.

Was this entry helpful?
Help us write better definitions. Quick reactions or detailed edit suggestions.
§

Test your knowledge

Q1. What are Recall Actions?

Q2. What can recall actions do?

Q3. Why design recall actions carefully?

§

Discussion

Loading…

Loading discussion…