Is it normal behaviour for an HTTP Request trigger in a flow to completely reject the incoming payload when it's body contains one or more backslashes ('\')?
Some weeks/months ago this wasn't an issue. We notice this for example when the body contains:
...
"lastUser": "DOMAIN\user",
...
Sending the webhook to webhook.site for example works without this limitation. Sadly we can't control the presence of the backslash in that key/value pair because it comes from a third party so at this moment our only option is to completely remove it from the webhook, leaving out valuable information.