Why does using escaping characters in Telegram API with Pipedream return an error?

Bugs
1

This topic was automatically generated from Slack. You can find the original thread here.

I’m testing RSS feed trigger and Telegram API with Pipedream but I got stuck into a possible bug, since the workflow (set with Parse Mode to MarkdownV2) works if I use in the Text box the follow:

{{steps.trigger.event.title}}
**xxx**

while it doesn’t work when using escaping characters:

{{steps.trigger.event.title}}
**xxx \** yyy*

and throws the error “ETELEGRAM: 400 Bad Request: can’t parse entities: Can’t find end of Bold entity at byte offset 50”

2

would you mind submit a ticket, stating steps to reproduce and screenshots?

3

I found out that is needed to put \ instead a single one , despite official telegram documentation