Facebook Lead Ads connection is repeatedly triggering old leads across 40 workflows

Hi, we are experiencing a serious issue with Facebook Lead Ads triggers.

Today I reconnected our Facebook Lead Ads connection while working on one specific workflow because the connection was not working correctly.

Immediately after reconnecting Facebook, all of our existing Facebook Lead Ads workflows started executing automatically. We have approximately 40 workflows connected to Facebook Lead Ads.

The triggers are not receiving new leads. Instead, each trigger is retrieving an old lead that had previously been captured.

The critical issue is that every time one of these old leads is triggered, Pabbly executes the entire workflow, including all subsequent actions.

As a result, old leads have been added again to our Google Sheets, sent again to Brevo and other connected systems, and automated welcome emails have been sent again to these contacts.

The issue is also repeating in cycles. The same old leads are being triggered and processed again without any new lead being submitted on Facebook.

I am providing the “Lead EMS Boca Raton” workflow and its Task History ID as a specific example so that your support team can investigate the issue. However, this issue is NOT limited to the Boca Raton workflow. All of our Facebook Lead Ads workflows using this connection have been affected by the same behavior.

For example, the Boca Raton workflow processed the same old lead at approximately 13:32 and again at 14:56, even though no new lead was submitted.

We have now used Bulk Disable to disable all affected workflows and stop further duplicate processing.

Could you please urgently investigate why reconnecting the Facebook Lead Ads connection caused all these triggers to repeatedly fire using previously captured leads and consequently execute the entire workflows?

Most importantly, we need to know whether it is safe to re-enable all our workflows without triggering another batch of old leads, as currently all of our Facebook Lead Ads automations are disabled.

Very thanks for the support.

Salvo Mattina:
Hi, we are experiencing a serious issue with Facebook Lead Ads triggers. Today I reconnected our Facebook Lead Ads connection while working on one specific workflow because the connection was not working correctly. Immediately after reconnecting Facebook, all of our existing Facebook Lead Ads workfl

The Facebook Lead Ads connection involved is a global/shared connection currently used by 161 workflows.

I reconnected this existing connection from inside one specific workflow (Boca Raton), as I was troubleshooting that workflow.

After reconnecting it from within that workflow, the issue affected multiple other workflows using the same shared Facebook Lead Ads connection.

This is particularly concerning because reconnecting a connection from within a single workflow appears to have impacted the shared connection globally and caused old captured leads to trigger and execute multiple workflows.

UPDATE: I performed an additional test by creating a completely new workflow from scratch.

I configured a new Facebook Lead Ads trigger for the Boca Raton form and put the trigger into waiting/capture mode.

I then submitted a brand-new lead through the Facebook Lead Form Preview using my own details (Salvo Mattina).

Facebook confirmed that the new form submission was successfully received.

However, Pabbly did NOT capture my newly submitted lead. Instead, it captured Steven Amoruso again, which is the previous/old Boca Raton lead that had already been processed.

Therefore, the issue also occurs on a completely new workflow and is not limited to our existing workflow configuration.

This seems consistent with the earlier issue where old leads were repeatedly triggering our workflows after the Facebook connection was reconnected.

As additional evidence, Facebook Leads Center confirms that my new test leads (Salvo Mattina) are being successfully received by Meta. Multiple new submissions appear for the Boca Raton form, including the latest one at 16:07.

However, when capturing the response in a completely new Pabbly workflow, Pabbly still returns the previous lead, Steven Amoruso, instead of any of these new leads.

This confirms that the new leads exist correctly on Meta's side, but Pabbly is retrieving an older lead.