Hey!
There’s a strange bug with Messenger behavior. The scenario that perfectly works in Telegram and Slack somehow shows no response in FBM.
Logs say that everything’s fine and the message WAS (at least should be) displayed, but there’s nothing in FBM.
That is the only “Bot - Send a message” trigger that does not work with FB in my flow which makes in even more weird.
Any thoughts?
Sorry to hear you’re having problems. We’ll check the basics first, did you click ‘Start’ when you opened up Messenger - you have to do that to open up a connection with the bot.
If you did that, could you attach some more info here, perhaps a screenshot of your flow setup? Any other info would be helpful.
Hope we can help you!
Thank you for the reply.
As I said, “that is the only “Bot - Send a message” trigger that does not work” in Messenger from this flow, so yes I definitely have clicked Start.
Here’s the screen of a flow, I don’t think it will give you much though.
But in the Messenger: there’s nothing:
(As you see the “error” trigger from my flow worked correctly and showed the response “Nope…” etc.)
The response pass for the missing message is also correct, I checked that (every step in the flow has the same one).
So that it all remains mystery 
(Sorry for the triple reply, forum rules do not allow new members to post more than 1 image at a time, which is annoying.)
It must be some content of the message - but it looks fine from what I can see. Please could you kindly send me (here or by direct message, or email support@flowxo.com) the exact contents of the message from the log (what is being sent but doesn’t arrive).
We’ll try and replicate this and fix whatever the problem is. Sorry you’re having trouble but rest assured we’ll figure out what’s happening!
So I understand you correctly, you say that this works perfectly in Slack and Telegram, but the last message fails in Messenger (but shows as sent?) If so this definitely sounds like some content that Messenger doesn’t like.
Thanks, I sent the message to support.
Yes that is correct.
We have been able to replicate this - it’s some content in the message. I’ve passed this to someone to fix, and I’ll keep you updated! Thanks 
