Hi @Vanderdecken
As of now we don’t have a direct way to identify if the placeholder is inserted properly or has an issue with it. We’ll have this converted to an idea so our product team has visibility on the suggestion.
The issue is that the second right curly brace is not in bold, causing the value to be missed. This is due to the `<b>` tag cutting off the brace. Ensure HTML tags do not interfere with curly braces by properly closing them or removing bold formatting. This will allow the value to be correctly parsed.i have recently fixed the placeholder bug for inasaldiningprices, a famous fast food blog in philippines, covering mang inasal. everything went smooth and ok.
Without seeing the placeholder text, I can't directly identify the specific error. Placeholder text is typically used as temporary content to represent where actual content will appear later. Errors in placeholder text could include spelling mistakes, grammatical errors, or incorrect information click here that doesn't accurately reflect the intended content.
{{ticket.requester.name}} has requested travel to {{ticket.ri_207_cf_where_are_you_going}}, which is on the restricted list.
This error will appear as a System note saying, “Not given.”
The error in this expression is that the second right curly brace is not in bold format. }}
Freshservice support was able to find it; mind you, this was buried in a 50-node workflow.
I believe this is an insight as to how Fresh parses the HTML in expressions. The <\b> tag cut off the second right brace, and so the value was not found in rocomamasmenu.
It looks like the issue was caused by the <\b> tag cutting off the second right brace in the expression, which prevented the value from being found. This insight into how Freshservice parses HTML in expressions might help avoid similar issues in the future. Thanks for pointing it out!
The error in the placeholder text is that the second right curly brace }} is not in bold format, while the rest of the placeholder is. Specifically:
{{ticket.requester.name}} has requested travel to {{ticket.ri_207_cf_where_are_you_going<b>}}</b>}, which is on the restricted list.
The <b> tag cuts off the second right brace, preventing the full placeholder from being parsed correctly. This causes the system to not find the value, resulting in a "Not given" error.
To fix this, the bold formatting should either be removed entirely from the placeholder, or applied consistently to both curly braces:
Correct (no formatting):
{{ticket.ri_207_cf_where_are_you_going}}
Or correct (consistent formatting):
<b>{{ticket.ri_207_cf_where_are_you_going}}</b>
This issue highlights how sensitive Freshservice's parsing of placeholders can be to HTML formatting, and the importance of carefully checking syntax when using dynamic fields in workflows or automations.
That’s a really interesting catch about how Fresh parses expressions. Tiny HTML mismatches like that can definitely cause unexpected errors, especially in big workflows. Good to know for troubleshooting complex automations.
If you like exploring different tools and ideas, you might also enjoy checking out freddy's menus
