I'm executing a campaign using the REST API and came across an interesting situation / issue.
When one of the token values passed in contains two hash / pound symbols consecutively "##" the token replacement / template "breaks" and unexpected results occur:
Value passed in: "PUcL#xPJE##0" (it's an auto-generated character sequence for a temporary password that happens to include the # as an option. In this case the random generator put two # together)
The value passed into the token above becomes the following in the e-mail received:
Thanks for any advice you can provide!