If you encounter issues while using the Security Center Extension, there are some troubleshooting batch configurations that can sometimes help you.
Data Classification
- Data Classification getFields: If the Data Classification table fails to load, open the developer console for your browser and look for an error labeled “CPU Time Limit Exceeded”. If the error is present, using the getFields metadata option in Batch Configuration sometimes fixes the issue. By default, getFields is set to a value of 10. Decreasing this value, pulling fewer objects at a time, helps to resolve page loading issues. Lower values increase load times. This is because fewer objects are pulled at a time.
- Data Classification Batch Promises: Select this option if the Data Classification tab fails to load. This option sometimes fixes the issue but increases load times.
- Number of Records Analyzed (Fill Rate Calculator): For larger orgs, decreasing the number of records analyzed when calculating the fill rate sometimes alleviates CPU Time Limit issues.
Security Insights
- Fill Rates Enabled: When experiencing timeout or heap size errors during the Fill Rates process, deselect this option.
- Field Exposure Batch User Access Rows: Controls the amount of User Access rows that are processed for a Field Exposure Batch job. Lowering this value sometimes fixes CPU timeout errors, especially with larger orgs.
- HighRiskFieldsAccessBatch: Controls the batch size during a Security Insights analysis job. Raising this value allows the batch to run faster while lowering the value sometimes fixes errors encountered during an analysis job.
- ExternalUserIDBatch: Controls the batch size during a Security Insights analysis job. Decreasing this value sometimes fixes heap size and CPU timeout errors encountered during an analysis job.
Who Sees What Explorer
- WSWE User Section Loading: If the Who Sees What Explorer fails to load properly, enable this option. This setting adds filters to only pull a subset of users at a time and sometimes fixes the issue, especially when dealing with larger orgs.
- WSW getFields: If the Who Sees What Explorer fails to load, open the developer console for your browser and look for an error labeled “CPU Time Limit Exceeded”. If the error is present, using the getFields metadata option in Batch Configuration sometimes fixes the issue. By default, getFields is set to a value of 10. Decreasing this value, pulling fewer objects at a time, helps to resolve page loading issues. Lower values increase load times. This is because fewer objects are pulled at a time.
- WSW Enable Time Machine: Selecting this option allows users to use the Time Machine feature within the Who Sees What Explorer.
- WSW getFieldPermissions: If you have users with a high number of permission sets, or the ability to assign many object and field-level permissions, this can sometimes cause an apex error while loading within the User Lens. Lowering the value of this batch configuration sometimes fixes the issue. This configuration will control how many permission set IDs are sent when retrieving field permissions for the user.