Skip to main content
January 8, 2018
Question

Rendered_Email_Velocity_Error_Area_?! error but no velocity scripting

  • January 8, 2018
  • 4 replies
  • 6061 views

I'm trying to send a sample of an email to test the rendering of a new template, and when I go to hit send on the sample, I get the following error:

I have no velocity scripting incorporated in this email. Even weirder? I tested the template in our sandbox instance and it worked just fine. Is this a glitch isolated to one instance? Is there something I'm missing?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

4 replies

Dan_Stevens_
Level 10
January 8, 2018

Do you a velocity script defined either within the program that contains this email; or at a higher-up parent folder (that the email could potentially inherit)?  If so - and there's an issue with the script - we've encountered similar errors like this in the past.

January 8, 2018

No, unfortunately there is no velocity script defined anywhere in this workspace

keithnyberg
Level 7
January 8, 2018

I agree with Dan's suggestion. Inherited tokens are probably the issue here.

January 8, 2018

There are no tokens, inherited or local, within this program.

SanfordWhiteman
Level 10
January 8, 2018

You (as in, we) are always using Velocity when assembling emails, whether or not there are any user-created tokens! So it is possible to get such errors simply by having certain Velocity reserved character sequences in a regular email.

Look for the # and $ characters in particular. If you whittle down the HTML chances are you'll find one of these is the problem, and I can tell you how to fix it.

January 9, 2018

It's a modular template referencing variables like ${body_color} throughout the code, so there are a lot of those types of characters. However, is there a reason it would pick up an issue with those character sequences in one Marketo instance and not another? As I mentioned in my original post, this email template works perfectly fine in our Sandbox account. It's only in production that I am experiencing this error message.

SanfordWhiteman
Level 10
January 9, 2018

Not all instances are equal w/r/t Velocity, unfortunately. (Almost equal but we see quirks now and then.)

When you whittle down the email to the offending part, what's the variable/syntax that's causing it?

Exequiel_Carriz
Level 2
May 2, 2018

Does anyone had a successful response about this? I'm experiencing the same issue with one of our templates.

SanfordWhiteman
Level 10
May 2, 2018

Did you read my post? This isn't a Velocity post, and yet it is