Skip to main content
Question

Messenger Automation Stopping Mid-Flow

  • December 27, 2025
  • 0 replies
  • 9 views

 

I’m encountering an issue with a Messenger automation that was working earlier today but started failing later in the day.

How the Automation Works

  • The automation sends individual job vacancy messages.

  • The number of messages varies (from 0 to any number).

  • Job data is stored in a Google Sheet.

  • Each row has a static identifier (not a formula), such as:

    • ABC-1

    • ABC-2

    • ABC-3, etc.

  • The automation looks up and sends jobs sequentially based on these identifiers.

Message Timing Setup

  • Each job listing is sent as a separate message.

  • There is a 3-second delay between each message.

  • Every 4th message has an additional “smart delay” of 10 seconds.

What Changed / What’s Going Wrong

  • Earlier today, the automation ran without any issues.

  • Later, I asked two friends to test the automation using their own Facebook accounts.

  • During testing:

    • The automation consistently stops after sending only 4 job listings.

    • It should send 6 job listings, but it never reaches the last two.

  • The failure happens after 6 consecutive messages are expected, but only 4 are delivered.

  • I refreshed permissions, but the issue persists.

Previous Observations

  • In the past, I noticed that:

    • Sending too many consecutive messages could cause the flow to stop midway.

    • Adding smart delays usually resolved this issue.

  • Previously:

    • Without smart delays → the flow would stop.

    • With smart delays → the flow could send up to ~20 messages successfully.

  • This makes today’s behavior confusing because:

    • Each message already has a 3-second delay

    • Every 4th message has a 10-second smart delay

Questions

  • Is there a daily or session-based limit on the number of Messenger automation messages?

  • Is Facebook/Messenger rate-limiting or throttling the flow due to:

    • Consecutive messages?

    • Testing with multiple user accounts?

    • Recent activity volume?

  • Could this be a Messenger platform enforcement rather than an automation logic issue?

  • How do I fix this?