If you encounter issues while using the Shield Extension, there are some troubleshooting batch configurations that can sometimes help you.
History Retention Policy Manager
- FHRP Objects per Fields Request: FHRP is the number of fields Secure requests in a single batch. A higher value sometimes causes an apex error. Lowering the value of FHRP sometimes fixes the issue.
Platform Encryption Analyzer
- ObjectRelationshipsBatch: Salesforce orgs with a large number of Object Relationships sometimes encounter heap size errors while running Platform Encryption Analyzer jobs. The default value for ObjectRelationshipsBatch is 200. Lowering the batch value sometimes fixes these errors.
- ShieldAcceleratorAnalyzerBatch: Large numbers of encryption blockers sometimes encounter heap size errors while running Platform Encryption Analyzer jobs for their Fields. The default value for ShieldAcceleratorAnalyzerBatch is 500. Lowering the batch value sometimes fixes these errors.
- PEA getFields: If the Platform Encryption Analyzer 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 because fewer objects are pulled at a time.
- FlowParserBatch: Large amounts of data in the Process Flows sometimes cause heap size errors while running Platform Encryption Analyzer jobs. The default value for FlowParserBatch is 50. Lowering the batch value sometimes fixes these errors.
- ReportFilterParserBatch: Having over 25,000 reports sometimes causes heap size errors while running Platform Encryption Analyzer jobs. The default value for ReportFilterParserBatch is 50. Lowering this value sometimes fixes these errors.
- PEA OrgSnapshot: Having a large number of fields sometimes causes heap size errors while running Platform Encryption Analyzer jobs. The default value for PEA OrgSnapshot is 200. Lowering this value sometimes fixes these errors.
- PEA Batch Promises: If the Who Sees What Explorer fails to load, open the developer console for your browse. Look for an error labeled Visualforce Exception or transaction aborted: timeout. If the error is present, using the PEA Batch Promises configuration option in Batch Configuration sometimes fixes the issue. By default, Batch Promises 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 because fewer objects are pulled at a time.