Known Issue : Permissions Issues following Salesforce Spring 21' Update

Known Issue

On February 13 and 14, 2021, Salesforce updated a number of Litify customers to the Salesforce Spring '21 seasonal release.

Since this update, some customers have reported errors similar to the following when making changes to Intakes or Matters:

  • "We can't save this record because XXXXXX process failed. Give your Salesforce admin these details. Profile does not have access to XXXXXX."



This issue occurs due to a known Salesforce bug specifically affecting orgs updated to Spring '21 on 2/13/2021 and 2/14/2021.

This issue causes custom automations such as Flows or Process Builders to fail when invoking Apex classes to which users have not been explicitly granted access.

Salesforce has acknowledged this issue and is reviewing a resolution.

Affected Orgs

This issue appears to affect only those Salesforce orgs updated to Spring '21 on 2/13/2021 and 2/14/2021.

Within that group, it further affects only Litify customers who have created custom Flows or Process Builders which call Apex classes that are not granted to users via profiles or permission sets.


Fortunately, this issue is easily resolved in either of two ways.

1. Easiest Method: Disable Rules for Enforcing Explicit Access to Apex Classes

Salesforce makes it possible to disable the change that they believe caused this issue with these simple instructions (also listed below):

Salesforce explains how to "Enable" this feature. Before permanently enabling this feature, you may test it first by clicking on "Enable Test Run" as shown below:


Once you "Enable Test Run", you should be able to re-test to see if your issue(s) have been resolved. If so, you can permanently activate this feature, by clicking "Done" and following the prompts. Make sure to click "Confirm" to apply the change. 




2. Alternate Method: Provide Access to Apex Classes Manually

You can provide the users seeing this error with access to the necessary Apex classes via their profile or a permission set.

The error message states which class is missing, so you can modify each Litify Profile that is used to add access to the class referenced in the error message.


Disable Rules for Enforcing Explicit Access to Apex Classes

Restricted Access Causing Flows to Fail in Spring 21





Was this article helpful?
1 out of 1 found this helpful