Hi ,
I see the following error in the delivery. What does this mean?
30/05/2018 22:21:20 Failed Unreachable xxxx@xxx.bham.ac.xxx Error while compiling script 'content htmlContent' line 6837: xtk is not defined. SCR-160012 JavaScript: error while evaluating script 'content htmlContent'.
Regards,
Priyanka
Solved! Go to Solution.
HI Priyanka,
You can ignore line number as sometimes it does not match with the line number of HTML code.
If recipient messages are failing with an "Unreachable" error stating: Error while compiling script 'content htmlContent' line X: [table] is not defined. JavaScript: error while evaluating script 'content htmlContent, the cause of this issue is almost always a personalization within the HTML attempting to call upon a table or field that has not been defined or mapped in the upstream targeting or in the delivery's target mapping.
To correct this, the workflow and delivery content need to be reviewed to determine specifically what personalization is attempting to call the table in question and whether or not the table can be mapped.
Check the all the personalization in html and from there, either removing the call to this table in the HTML or fixing the mapping to the delivery would be the path to resolution.
You can go through below links to know more on this
Hi Priyanka,
Generally such errors are due to delivery content issue and for which you have to review the html content.
Are you facing this issue with this particular recipient or it is failing for all the recipients.
Hi Shrawan,
OK.but there is no line 6837 in the html code, so was confused on how to debug.Yes, this is the issue for all recipients.
Regards,
Priyanka
Views
Replies
Total Likes
HI Priyanka,
You can ignore line number as sometimes it does not match with the line number of HTML code.
If recipient messages are failing with an "Unreachable" error stating: Error while compiling script 'content htmlContent' line X: [table] is not defined. JavaScript: error while evaluating script 'content htmlContent, the cause of this issue is almost always a personalization within the HTML attempting to call upon a table or field that has not been defined or mapped in the upstream targeting or in the delivery's target mapping.
To correct this, the workflow and delivery content need to be reviewed to determine specifically what personalization is attempting to call the table in question and whether or not the table can be mapped.
Check the all the personalization in html and from there, either removing the call to this table in the HTML or fixing the mapping to the delivery would be the path to resolution.
You can go through below links to know more on this
Hi Shrawan,
Thanks for all the inputs . I would also like to add one more point . This issue is seen only when we use Continuous Delivery and not in the regular email delivery. What could be the reason?
Regards,
Priyanka
Views
Replies
Total Likes
Hi,
Any reply pls?
Regards,
Priyanka
Views
Replies
Total Likes
Hi Priyanka,
Ideally that should not be the case. If it is working with email delivery, then it should work with continuous delivery also.
I would suggest you to raise the ticket with campaign support for further help on this
Views
Replies
Total Likes
Hi Shrawan,
Ok thanks.
Regards,
Priyanka
Views
Replies
Total Likes
Hi Priyanka,
Got any solution?
Are you using any variables inside continuous delivery? If so then error in the variable which you are using.
Thanks
Naveen
Views
Replies
Total Likes
Views
Likes
Replies