Troubleshooting
Find solutions for Plauti Verify errors, access issues, flow configuration problems, legacy naming, and changes to navigation and validation results.
No access to Verify Apex Classes
Resolve Plauti Verify Apex class access errors by enabling profile settings, granting missing classes, and assigning the Verify Permission Set to prevent issues after updates.
Apex error in record-triggered flow
Resolve record-triggered flow callout errors by configuring the flow to run asynchronously after the triggering record transaction is committed.
Cannot find the job results filter
The Results Page no longer has a filter; learn how to sort records by validation status using the Validated, Needs Decision, or Unable to Validate column headers.
Attempt to de-reference a null object error
Learn how to troubleshoot “Attempt to de-reference a null object” errors by checking deleted or empty field references in Record Validation Setup and Flow configurations.
RV Entry / Verify Entry tab no longer supported
Learn why the RV Entry/Verify Entry navigation tab is no longer supported and how to use the Plauti Verify Entry replacement page instead.
RV and Plauti Verify old and new names
Learn how Record Validation became Plauti Verify, which labels changed, which technical identifiers remain unchanged, and how to handle exceptions and legacy names.
Cannot use apex actions in immediate path flow
Problem: My record-triggered flows for Plauti Verify that contain a Plauti apex action don't work anymore. When creating a record-triggered flow with a Plauti apex action, it will not save.