Loading

Assignment rules are firing unexpectedly

Publiseringsdato: Jun 14, 2026
Beskrivelse

When using the Salesforce REST API to create or update records (such as Cases, Leads, or Accounts), assignment rules may fire unexpectedly, changing record ownership in ways that were not intended. This occurs because the Sforce-Auto-Assign HTTP request header defaults to TRUE when it is not explicitly included in a REST API request. As a result, any REST API operation that omits this header will trigger assignment rules automatically.
As documented in the REST API Developer Guide, the default value of Sforce-Auto-Assign is TRUE unless explicitly set to FALSE.

Løsning

Primary Fix: Set Sforce-Auto-Assign to False

Include the Sforce-Auto-Assign: FALSE header in all REST API requests where assignment rules should not run. This explicitly prevents assignment rules from firing for that operation.

Known Exceptions Where the Header Cannot Be Controlled

Certain Salesforce standard features that use the REST API internally do not expose the ability to control the Sforce-Auto-Assign header. In these cases, assignment rules will always fire. Known examples include:

  • Cross-Org Connect (External Objects): Updates made via External Object connections use the REST API without exposing the header.
  • Developer Console: Record updates performed through the Developer Console use the REST API without the ability to set the header.
  • Lightning for Outlook: Record creation and updates via the Lightning for Outlook add-in do not support customizing this header.

Note on Case records: For Case records, when assignment rules are triggered but no rule entry matches the case criteria, the case owner is changed to the Default Case Owner configured in your Support Settings.

Knowledge-artikkelnummer

000390059

 
Laster
Salesforce Help | Article