Skip to main content

Hello, 

As can be seen above, I have a Messenger Automation live that has “0” Runs. Users are commenting the correct Keywords and are receiving the auto-reply comment but are not receiving the DM in Messenger. This has happened for several of my previous Automations with the same set up. This has only started happening in the last few weeks. Prior to this, the same set up was working fine. 

Any idea what might be causing this issue? 

Some things that may be useful to know: 

  • I refreshed permissions for FB after this went live but it didn’t have an effect.
  • Instagram Automations of the same type are working fine without issue.
  • I do delete my all my contacts on a regular basis.

After refreshing my permissions I now have the below error message pop up but sure if relevant. I tried to address this following the instructions but was unable to do so. 

“Your Facebook Conversions API (CAPI) integration has been disconnected. To keep your data flowing, please reconnect it manually.”

Thanks a million :)
AJ

 

Hey ​@LovelyIrishAlan I suggest you try it first with a very simple reply, just saying ‘it works’ and nothing more (no links or copy).

If that doesn’t work, the connection is broken. Refresh Permissions, reconnect, or talk to the support team to see what’s going on and sort this out.

If it works, then the issue is your content.

Either your copy or the links you’re sending are causing Facebook to detect your message as unsafe/scammy/not allowed/or whatever, and Facebook is basically deciding not to deliver it.

If that’s the case, the game becomes to find what exactly is the content that causes the issue.

I’d start the test with the same copy and no links, and see how that works.

And then start adding items, one by one, until you find what’s causing the issue.

Hope this helps!!

Hi, I’m having an issue with my auto DM flow.
The first DM I set up gets sent correctly,
but when users click the “Follower / Non-Follower” button,
the next message in the flow doesn’t get delivered.

If you’ve already solved this issue before,
could you please share how you fixed it?

Community Terms & ConditionsCookie settingsAccessibility statement