This article covers methods to resolve errors and timeout issues within the Platform Encryption Analyzer (PEA) tab. To use the following settings, a new Batch Configuration must be created, or edit an existing one. If any options shown are missing, the page layout for Batch Configuration must be edited.
ObjectRelationshipsBatch
Salesforce Orgs with large amounts of Object Relationships may encounter heap size errors while running PEA jobs. The default value for this configuration is 200. Lowering the batch value may remedy these errors.
ShieldAcceleratorAnalyzerBatch
Salesforce Orgs with large amounts of encryption blockers may encounter heap size errors while running PEA jobs for their Fields. The default value for this configuration is 500. Lowering the batch value may remedy these errors.
PEA getFields
If the PEA table fails to load, please open the developer console for your browser. Not all browsers use the same key combination, so do a quick Google search for your preferred browser if the following does not work:
Chrome:
- Cmd + Option + J (Mac)
- Ctrl + Shift + J (Windows)
Firefox:
Safari:
- Cmd + Option + C (Mac)
Edge:
- Ctrl + Shift + I (Windows)
Look in the developer console for an error labeled “CPU Time Limit Exceeded”. If the error is present, using the getFields metadata option in Batch Configuration may alleviate the issue. The default value for this configuration is 10. Decreasing this value, pulling fewer objects at a time, helps to resolve page loading issues.
FlowParserBatch
Salesforce Orgs with large amounts of data in their Process Flows may encounter heap size errors while running PEA jobs. The default value for this configuration is 50. Lowering the batch value may remedy these errors.
ReportFilterParserBatch
Salesforce Orgs with over 25,000 Reports may encounter heap size errors while running PEA jobs. The default value for this configuration is 50. Lowering this value may remedy these errors.
PEA OrgSnapshot
Salesforce Orgs with a large amount of fields may encounter heap size errors while running PEA jobs. The default value for this configuration is 200. Lowering this value may remedy these errors.
PEA Batch Promises
Look in the developer console 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 may alleviate the issue. The default value for this configuration is 10. Decreasing this value, pulling fewer objects at a time, helps to resolve page loading issues.
Create Batch Configuration Custom Metadata in Secure
Batch Configuration Page Layout Editor for Secure