Loading

Salesforce Financial Services Cloud: FinServ trigger fails with "Access Blocked Requires Extra Verification"

Julkaisupäivä: Jul 13, 2026
Kuvaus

In Salesforce Financial Services Cloud (FSC), users may be unable to create or update records such as Opportunities, Tasks, and Financial Holdings, and flows that touch these objects fail during execution. The failure surfaces as an Apex unhandled trigger exception thrown by the FSC managed package. A representative error is:

CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY: FinServ.OpportunityTrigger: execution of BeforeUpdate caused by: FinServ.MoiExceptionWrapper.TriggerException: Something's not quite right. Try your action again, and if the issue continues, contact your administrator for help.: Access Blocked Requires Extra Verification (System Code) Caused by (System Code).

The same class of error can appear on other FSC triggers, for example FinServ.FinancialHoldingTrigger: execution of BeforeInsert caused by: FinServ.MoiExceptionWrapper.TriggerException.

"Access Blocked Requires Extra Verification" is a platform step-up (High Assurance) session response, not an FSC-specific defect. It occurs when a Session Security Level Policy is set to require additional identity verification (Raise session to high assurance, or Block) for an operation, and the operation runs in a session that does not meet that assurance level. When the managed-package trigger performs a sharing-related operation, the Manage Sharing session security level policy causes the platform to demand extra verification, which blocks the DML. The behavior affects all users performing the impacted create/update actions and can appear after a Salesforce release or a change to session security policies.

Ratkaisu

Cause
The Manage Sharing session security level policy is set to require additional verification (Raise session to high assurance, or Block). This policy controls access to sharing-related operations, and the Financial Services Cloud managed-package trigger performs a sharing operation during the DML. When the current session does not meet the required assurance level, the platform returns "Access Blocked Requires Extra Verification" and the trigger fails.

Set the Manage Sharing session security level policy to None
1. From Setup, in the Quick Find box, enter Identity Verification and select Identity Verification.
2. Scroll to the Session Security Level Policies section.
3. Locate the Manage Sharing policy.
4. If it is set to Raise session to high assurance or Block, change it to None.
5. Save the change.

Important - security consideration
Setting Manage Sharing to None removes the step-up (High Assurance) requirement for sharing-related setup operations across the org. Evaluate the security impact before applying this change. As alternatives, ensure the affected users hold a High Assurance session for the operation, or restrict the change to the minimum required, rather than broadly disabling the policy.

Verify the fix
1. As an affected user, create or update an Opportunity or Task that invokes the Financial Services Cloud managed-package trigger.
2. Re-run any flow that previously failed on Opportunity or Task DML.
3. Confirm the record saves and the flow completes without the "Access Blocked Requires Extra Verification" error.

Knowledge-artikkelin numero

005388915

 
Ladataan
Salesforce Help | Article