Loading

Salesforce Session Security: "High Assurance" Level Blocks Asynchronous Apex Processing

Дата публикации: Jun 11, 2026
Описание

Overview

When a user's Profile has "Session Security Level Required at Login" set to "High Assurance," asynchronous Apex operations will fail. Asynchronous operations that are blocked include Apex future methods, Apex callouts, and getContentAsPDF().
The "High Assurance" setting in a Profile refers to the requirement configured in Setup > Session Settings > Session Security Levels. This setting may have "Multi-Factor Authentication" or other options set to High Assurance. These High Assurance session settings are intended for synchronous and UI-based processing only — they do not support asynchronous processing contexts such as Apex future jobs, batch jobs, or scheduled jobs.

Решение

Recommended Workaround

If Multi-Factor Authentication (MFA) is required, use the "Multi-Factor Authentication for User Interface Logins" system permission on the user's Profile or Permission Set instead of setting "High Assurance" under the Profile's "Session Security Level Required at Login." For this workaround to function correctly, the "Session Security Level Required at Login" must be set to None.

Steps to Apply the Workaround

  1. Navigate to Setup > Profiles (or Permission Sets).
  2. Edit the affected Profile or Permission Set.
  3. Enable the "Multi-Factor Authentication for User Interface Logins" system permission.
  4. In the same Profile, locate "Session Security Level Required at Login" and set it to None.
  5. Save the changes.
  6. Re-test the asynchronous Apex operation to confirm it runs successfully.
Номер статьи базы знаний

000392426

 
Загрузка
Salesforce Help | Article