ACORD form errors
Last updated: September 21, 2026
Overview
Most ACORD form errors that come up during generation trace back to a single cause: an issue with the user's API token. This token manages the connection between Salesforce and the external tool that houses and maps ACORD forms, and each user needs their own working token for the integration to function correctly. Use this article to work through token-related errors.

Resolving the error
Use one of the three methods below to resolve the error, starting with the simplest and moving to the next if the issue persists.
Clear cookies from forms window
Right click on the ACORD forms pop-up window and click Inspect. This opens Chrome DevTools.

Click the Application tab.

Under Storage in the left-hand menu, expand the Cookies section.
Right-click the entry and click Clear.

If the cookies are successfully cleared, the Chrome Dev Tools screen should show this:

Note: Clearing cookies within the ACORD forms app doesn't affect your entire browser, and you won't be logged out of any open sessions.
2. Clear browser cache
For guided steps, see 📄 How to clear your cache.
Manually reset the API token
If the issue persists after clearing the cache, manually reset the affected user's API token.
Log in as an admin user or a user with permissions to manage other users.
Click the gear icon in the top right corner and select Setup.
In Quick Find, search for and select Users.
Find the affected user's profile and click into it.
Click Edit.
In the Veruna API Token section, locate the VerunaApiToken field and delete all text in the field.
Save your changes.
Re-establish the token
With the token removed, the user can reauthenticate to generate a new one.
Log into the system.
Open any policy page.
Click the ACORD Cancellation button in the actions header.
Follow the prompts to accept and configure a new API token.
Best practice: End-of-day session management
Log out of Salesforce or closer your browser completely at the end of each day.
Salesforce authorization tokens expire after a period of inactivity, but the session cookie can remain active longer.
If the browser stays open, this mismatch can make Salesforce appear "logged in" while the Forms app fails due to an expired token.
Closing the browser or logging out clears the session cookie, so you're automatically re-authenticated with a fresh token each time.
Note: If the issue persists after completing these steps, contact support@amplo.com to reset the token at the org level.