Resolving VerunaDocs errors
Last updated: October 22, 2026
Overview
VerunaDocs errors occur for various reasons. Use this article to work through general troubleshooting steps and find targeted fixes for specific error messages.
Note: To maintain consistent access to VerunaDocs, use Chrome or Edge, keep your browser updated, and log out and back into Salesforce if you haven't done so in several days.
Initial troubleshooting steps
If you are having trouble attaching documents or emails to accounts, start here.
Clear your browser cache. This often resolves temporary upload or UI-related issues. See 📄 How to clear your cachefor instructions.
Restart your browser by fully closing all windows and reopening.
Log out and log back into Salesforce to refresh your session.
Try the attachment again. The issue may resolve on its own after the above steps.
Check your browser's pop-up blocker settings. Pop-up blockers can prevent VerunaDocs from opening document windows and uploading files. Ensure pop-ups are allowed for your Salesforce domain.
Common Errors
If the steps above don't resolve the issue, select your specific error for targeted troubleshooting:
Note: If a large batch of documents doesn’t arrive by email, each user needs to open an account’s Documents tab and click Allow when prompted.
Additional Troubleshooting Steps
If the issue persists, try the following:
Note which specific accounts are affected.
Remove special characters from subject lines. Prefixes like "RE:" or "FWD:" may interfere with attachment processing.
Test different file types to determine if the issue is file-specific.
Check whether other users in your org are experiencing the same issue.
Note: If you see an embedded page error when attaching a document, refer to 📄 Resetting the VerunaDocs API token for more information.
Note: There's a known issue with special characters in subject lines currently being investigated with our team.
When to contact support
Reach out to support@amplo.com if the issue persists after completing the steps above, if multiple users are affected, or if the problem occurs across different accounts or document types.
When submitting a request, include:
Names of affected users
Direct links to the impacted accounts
Screenshots of any error messages
A list of troubleshooting steps already completed