Facebook Lead Ads Repeatedly Triggering the Same Old Leads – Task Credits Exhausted & Client Notifications Duplicated

Hi Pabbly Team,

I am facing the same serious Facebook Lead Ads issue reported by several other users here.

Today, my Facebook Lead Ads workflows started triggering the same previously received leads repeatedly at different times, even though no corresponding new lead was submitted.

For example, one of my client leads was processed repeatedly at approximately 4:49 PM, 5:51 PM, 6:53 PM, 7:11 PM, 7:21 PM and 7:34 PM. Each time, the workflow executed again and sent the same lead notification to WhatsApp.

This caused two major problems for us:

1. Our Pabbly task credits were consumed unnecessarily because the same leads were repeatedly executing the workflows.

2. Our clients received the same lead notifications multiple times, and we started receiving complaints from them.

This is particularly serious because we use Pabbly Connect for live lead automation for multiple clients. These are real Facebook advertising leads, so simply stopping all workflows also creates a risk of missing genuine new leads.

Because my task credits were unexpectedly consumed by these repeated executions, I had no practical option but to purchase/activate the Pabbly Connect Monthly Plan – Tier 1 for ₹2,122.83 to keep our live client lead automations running and avoid missing genuine leads.

I have now seen Pabbly Support confirm in this community that the current Facebook Lead Ads version has been deprecated by Meta and that this has caused unexpected behavior in the existing integration. Pabbly has also confirmed that the Technical Team is aware of the issue and is working on a fix.

My issue appears to be consistent with what other users are reporting here: old/already processed leads are being treated as new leads and the downstream workflow actions are being executed again.

I urgently need clarification on the following:

1. Is it currently safe to keep Facebook Lead Ads workflows enabled?

2. If I keep them enabled, can the same old leads continue triggering and consuming tasks?

3. During this incident, is there any possibility that genuine new Facebook leads were not retrieved or were skipped by Pabbly?

4. How can we identify and recover any genuine leads that may have been missed?

5. Will Pabbly restore the task credits consumed by these duplicate executions?

6. Since I had to pay an additional ₹2,122.83 only to keep my client workflows operational after the unexpected task consumption, how will Pabbly address this payment?

7. When is the fix expected to be deployed, and how will we know when it is safe to run/re-enable all affected workflows?

I can provide screenshots showing the same lead being sent repeatedly at different timestamps, my Task History, and proof of the ₹2,122.83 payment.

Please escalate this to the Technical and Billing Teams. This is affecting our live client operations, consuming paid task credits, generating client complaints, and potentially putting genuine incoming leads at risk.

Please also confirm once the issue has been fixed and it is safe to run Facebook Lead Ads workflows again.

Regards,
Sangeeth G Sivan
Managing Director
Brandvaro Innovations Pvt Ltd

Since this morning, the "Facebook Lead Ads: New Lead (Polling)" trigger has been re-running OLD leads across our ~300 workflows, even though no new leads have been submitted.

• You acknowledged the issue today on your community forum and stated that a Meta version change broke the integration. Many other users have reported the same problem since 08:49.

• Example: the "Ciudad España" workflow has only 1 lead in the last 90 days, yet it ran 8 times in 40 minutes.

• Each run re-sent old and test leads ("Max Prueba") to our clients, and also triggered emails and CRM entries.

TASK CONSUMPTION

• Tasks consumed so far: 64,478

• Tasks remaining: 35,522

• At the current rate, our quota would have been exhausted by tonight.

• We have already deactivated all affected workflows as of [time] to stop the consumption.

WHAT WE NEED

1. A refund or restoration of all tasks consumed today by these duplicate executions. The cause is a platform failure, not our configuration.

2. Protection of our task quota until the fix is deployed.

3. An estimated timeline for fixing the Polling trigger.

4. A bulk switch of our workflows from "New Lead (Polling)" to "New Lead (Instant)" on your end. Manually editing ~300 workflows is not feasible for us.

5. Explicit confirmation of when it is safe to reactivate the workflows without old leads being triggered again.

This is affecting live communication with our real estate clients, so we would appreciate a priority response.

Thank you,