'Not Allowed - Token key not found' Error when Approving an Email Asset

A document by KCS Integration on behalf of Avery Nason on Nov 20, 2019Last modified by Roxann McGlumphy on Nov 22, 2019
Version 2Show Document
  • View in full screen mode

Issue Description
You're receiving an error that states 'Not Allowed - Error approving <asset-name> - {{token-name}} : Token key not found' when trying to approve an email asset.

 

Issue Resolution
The reason you are seeing this error is because the token mentioned in the error does not exist in the asset. To fix this error, you will want to remove this token from the asset. This can be done by choosing to edit the asset and searching the code of the asset for the token in question, and finally removing this token from the HTML of the email.  If you do not find it in the HTML, check the text-only version as well.

 

This commonly happens when the asset is not in the same program as a my.token referenced in the email. 

Attachments

    Outcomes