Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
@SanfordWhiteman Thank you for sharing your experience. I understand that VTL itself shouldn't cause any issues.Marketo Support shared the knowledge base link below, stating that the limit applies to VTL and that the email could fail to send if exceeded. However, it's hard for me to accept this blin...
@SanfordWhitemanThere were no issues with the Velocity Script. The records were marked as "Marketing Suspended" and will be removed once the email is verified. I didn’t set the email as operational, so Marketo skipped the flow step. Thankfully, there was nothing major. Could you please confirm my qu...
@SanfordWhitemanIt appears there is an issue with the Velocity script. Within the script, I'm checking whether the consent fields are set to true in order to display the unsubscribe link. When none of the consent fields are set to true, the email is skipped in the flow step I believe. I'll review th...
Hi @SanfordWhiteman To add further context to my testing regarding the email not being sent — it appears that Marketo is skipping the "Send Email" step and proceeding to the next step. Why would Marketo skip this step?Thank you!
Hi @SanfordWhiteman During my testing, emails using Velocity scripting with a large number of custom field variables (tokens) were not delivered. In my case, I used 42 custom field variables.I added a 1-minute wait step before the Send Email step, and then the email was sent successfully. However, t...
I understand that there's a limit of 40 custom field tokens that can be used directly in a Marketo email. If this limit is exceeded, Marketo throws an error indicating that the token limit has been crossed. I'm curious whether using more than 40 custom tokens in a Velocity Script could cause any iss...