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.

Additional update with further evidence:

I have now confirmed that this is not only an issue with the response shown during trigger configuration.

Facebook Leads Center correctly shows my new test submissions (Salvo Mattina), including a new submission at 16:07 for the Boca Raton form.

However, the existing Boca Raton workflow automatically executed again at 16:13:36, and the Facebook Lead Ads trigger processed Steven Amoruso, an old lead that had already been processed previously.

The same workflows continue to execute periodically without new corresponding leads being submitted. For example, Boca Raton executed again at approximately 16:24, and Novara also executed again.

Therefore, Pabbly is not simply displaying cached sample data during setup. The Facebook Lead Ads trigger is actually treating old leads as new leads and executing the downstream workflow actions again.

I have now disabled the affected Facebook Lead Ads workflows again to prevent further duplicate processing.

Please also note that the Facebook Lead Ads connection involved is a shared connection used by 161 workflows. The problem started after this existing connection was reconnected while troubleshooting one workflow.

Before we re-enable these workflows, we urgently need confirmation of:

1. Why old Facebook leads are being repeatedly triggered as new leads.

2. Why newly submitted leads visible in Facebook Leads Center are not being retrieved by Pabbly.

3. Whether it is safe to re-enable the affected workflows.

4. Whether the shared Facebook Lead Ads connection needs any action from your technical team without reconnecting it again, since reconnecting it appears to have triggered this issue across multiple workflows.

I can provide the specific Task History IDs and screenshots showing the old lead being processed again if needed.

i have same problems.

we need response from pabbly team immediatly!

Hello Salvo,

Thank you for reaching out and sharing the details of the issue you are facing. We completely understand the seriousness of the situation and sincerely apologize for the inconvenience caused.

Please note that the current version of Facebook Lead Ads has been deprecated by Meta, which has led to unexpected behavior in the existing integration. Our Technical Team is already aware of this issue and is actively working on a fix.

We assure you that we will inform you immediately once the issue is resolved. In the meantime, we truly appreciate your patience and understanding.

Thank you for the update and for confirming that your technical team is aware of the issue.

Before I can plan around this, I need answers on four points that the update does not cover.

First, the trigger is not only re-sending old leads, it is failing to retrieve new ones. Another customer documented this in thread 218269: a brand new lead submitted through the Facebook form appears correctly in Meta Leads Center, but the trigger returns a previously processed lead instead. Please confirm whether leads submitted during this incident are being skipped entirely, and how they will be recovered once the fix is deployed.

Second, please provide an expected timeframe for the fix, even an approximate one. I have over 1,600 active workflows delivering leads to clients and I need to tell them what to expect.

Third, my account consumed its full 12,000 task allotment on duplicate executions in roughly three hours today. Please confirm that these tasks will be refunded.

Fourth, my workflows stopped only because the task quota ran out, not because the issue was resolved. Please confirm whether the duplicate executions will resume when my quota renews or if I upgrade the plan. I am holding off on any upgrade until I have this in writing.

I have not reconnected the Facebook Lead Ads connection and will not do so until you confirm it is safe.

Im facing the same issue as the other users explained

Desde esta mañana, el disparador "Facebook Lead Ads: New Lead (Polling)" está volviendo a ejecutar leads ANTIGUOS en nuestros ~300 flujos de trabajo, sin que se haya enviado ningún lead nuevo. - Ustedes reconocieron el problema hoy en su foro de la comunidad. Indicaron que un cambio de versión de Meta rompió la integración. Muchos otros usuarios reportan lo mismo desde las 08:49. - Ejemplo: el flujo "Ciudad España" tiene solo 1 lead en los últimos 90 días, pero se ejecutó 8 veces en 40 minutos. - Cada ejecución volvió a enviar leads antiguos y de prueba ("Max Prueba") a nuestros clientes, además de correos y registros en el CRM. CONSUMO DE TAREAS - Tareas consumidas hasta ahora: 64.478 - Tareas restantes: 35.522 - Al ritmo actual, nuestro cupo se habría agotado esta noche. - Ya desactivamos todos los flujos afectados, a las [hora], para detener el consumo. LO QUE NECESITAMOS 1. Que nos reembolsen o restituyan todas las tareas consumidas hoy por estas ejecuciones duplicadas. La causa es una falla de la plataforma, no de nuestra configuración. 2. Que protejan nuestro cupo de tareas hasta que la solución esté implementada. 3. Un plazo estimado para la corrección del disparador Polling. 4. Que cambien nuestros flujos de "New Lead (Polling)" a "New Lead (Instant)" de forma masiva desde su lado. Editar ~300 flujos manualmente no es viable para nosotros. 5. Que nos confirmen explícitamente cuándo es seguro reactivar los flujos sin que se vuelvan a disparar leads antiguos. Esto está afectando la comunicación en vivo con nuestros clientes inmobiliarios, por lo que agradeceríamos una respuesta prioritaria. Gracias,

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,

Same issue on our account — ~300 workflows affected.

We had to manually disable all of them this morning because they started re-processing and duplicating historical leads. Old leads were sent again to our clients' CRMs, Google Sheets and email lists, even though no new leads had been submitted. The workflows are still OFF.

@Pabbly team: can you please share an ETA for the fix?

We need to know:

1. When will the Facebook Lead Ads trigger be fixed?

2. Once fixed, will it be safe to re-enable workflows as they are, without duplicating historical leads again? Or do we need to reconnect or switch each one to "New Lead (Instant)"?

3. Will tasks consumed by the duplicate runs be credited back?

Please post an update here as soon as it's resolved. Thanks!

Hi Mario,

Was this resolved for you? I am experiencing the same issue.

Hello Sajid,

Thank you for reaching out and sharing the details of the issue you are facing. We completely understand the seriousness of the situation and sincerely apologize for the inconvenience caused.

Please note that the current version of Facebook Lead Ads has been deprecated by Meta, which has led to unexpected behavior in the existing integration. Our Technical Team is already aware of this issue and is actively working on a fix.

Also, once the issue is fixed, the leads that were not received during this period will be processed, so no leads will be missed.

We assure you that we will inform you immediately once the issue is resolved. In the meantime, we truly appreciate your patience and understanding.

Sajid Bari:
Hi Mario, Was this resolved for you? I am experiencing the same issue.

No, I'm still waiting.

Sajid Bari:
Hi Mario, Was this resolved for you? I am experiencing the same issue.

Pabbly Support:
Hello Sajid,Thank you for reaching out and sharing the details of the issue you are facing. We completely understand the seriousness of the situation and sincerely apologize for the inconvenience caused.Please note that the current version of Facebook Lead Ads has been deprecated by Meta, which has

Pabbly Support:
Hello Sajid,Thank you for reaching out and sharing the details of the issue you are facing. We completely understand the seriousness of the situation and sincerely apologize for the inconvenience caused.Please note that the current version of Facebook Lead Ads has been deprecated by Meta, which has

Please provide information regarding the timeline for resolving this major problem.

Pabbly Support:
Hello Salvo,Thank you for reaching out and sharing the details of the issue you are facing. We completely understand the seriousness of the situation and sincerely apologize for the inconvenience caused.Please note that the current version of Facebook Lead Ads has been deprecated by Meta, which has

Please provide information regarding the timeline for resolving this major problem.

Hello Mario,

The Team is investigating the issue, and it may take another 10-15 hours to fix it. We will inform you once the issue is resolved.

Same here, big issue!

Same Here!

same here

Same here, big issue. Can we get a timeline on when this will be fixed? Impacting all opertions

Hi Pabbly Support Team,

We are also experiencing a serious issue with the Facebook Lead Ads triggers in our Varma Homes marketing workflows.

Yesterday, we noticed that the latest Facebook leads are not being captured in Google Sheets, while the Pabbly triggers are instead retrieving previously captured/old leads.

We are also facing the same issue after reconnecting the Facebook Lead Ads connection. We have multiple workflows connected to Facebook Lead Ads, and the triggers appear to be picking up old leads rather than the newly generated leads.

The critical concern is that whenever an old lead is triggered, Pabbly executes the entire workflow, including all subsequent actions. This can result in duplicate entries being added to Google Sheets, leads being sent again to Brevo and other connected systems, and automated welcome emails being sent repeatedly to existing contacts.

Could you please investigate this issue urgently and let us know:

• Why the Facebook Lead Ads triggers are retrieving old leads instead of new leads.

• Why yesterday's/new leads are not being captured in Google Sheets.

• Whether reconnecting the Facebook connection is causing previously processed leads to be triggered again.

• How we can prevent duplicate workflow executions and ensure only new leads are processed.

Since this is affecting our live lead-generation workflows, we would appreciate your urgent assistance in resolving this issue.

Thank you.

try chage trigger to "instant lead".

looklike it solved.

Any updates

Could you please check this issue on priority? I am still facing the same issue, and it is impacting our ability to run the business operations smoothly. Kindly investigate and resolve this at the earliest.

Hello,

Please note that the Facebook Lead Ads – New Lead trigger is currently facing an issue due to changes and deprecation of the Facebook API. As a result, the trigger may fetch or process older leads as well.

Our team is already working on the required changes, and we expect this issue to be resolved by EOD today. Once the changes are implemented, the trigger should work as expected.

We apologize for the inconvenience caused.

As an alternative, you can currently use the “New Lead (Instant)” trigger event under Facebook Lead Ads. Please note that for this trigger, you will need to connect the Facebook account of the Page owner. It will not work with Admin account access.

We hope this clarifies the situation. If you have any other concerns or need further assistance, please feel free to let us know. We’ll be happy to assist you.

I am gradually turning on my workflows, and it seems they have started working correctly.

Salvo Mattina:
I am gradually turning on my workflows, and it seems they have started working correctly.

The problem has happened again. I’ve turned off the workflows again. Any updates?

This issue is also consuming a significant number of Pabbly tasks unnecessarily, as each old lead triggers all the subsequent steps in the workflow.

We hope that the tasks consumed because of this confirmed technical issue can be restored or credited back to our account, as they were not generated by legitimate workflow executions.

Please confirm when the technical fix has actually been deployed and when it is safe for us to re-enable our workflows.

Please provide information regarding the timeline for resolving this major problem. Is it resolved??????

Hello,

There was an issue with the Facebook Lead Ads – New Lead trigger event, which caused the issue you experienced. We apologize for the inconvenience.

The issue has now been resolved. Please check on your end and confirm if the trigger is working as expected.

If the issue still persists, please let us know, and we will be happy to assist you further.

URGENT: The issue is NOT resolved.

We re-enabled the workflows after your confirmation that the issue had been fixed. Unfortunately, the problem immediately started again.

As you can see in the attached screenshots, our Legnano Facebook Lead Ads workflow executed at least 8 times within approximately the same second (14:11:26–14:11:27).

These executions processed old leads again and inserted them again into our Google Sheet. The same old contacts are also being sent again to Brevo, which means that these people are receiving our automated welcome email again, even though they had already received it previously.

This is therefore not only creating duplicate data and consuming tasks, but is also directly affecting our customers and leads by sending duplicate communications.

We are disabling all Facebook Lead Ads workflows again immediately.

Please escalate this urgently to your technical team. At this point we cannot safely re-enable our workflows based only on confirmation that the issue has been resolved.

We are also continuing to consume a significant number of Pabbly tasks because every duplicate execution runs all subsequent workflow steps. Please confirm that the tasks consumed as a result of this technical issue will be restored or credited to our account.

Please let us know only when the fix has been fully deployed and verified, as this is currently affecting our production lead management across multiple locations.

Hello Salvo,

I would like to inform you that the issue has been resolved. Kindly turn on the workflow, and it will fetch the new leads now.

Further, you can let us know the tasks consumed due to this issue, our team will review and reset those tasks for your account.

Hi, thank you for the update.

The issue now seems to be resolved, at least for the moment, and the Facebook Lead Ads workflows appear to be working correctly again.

However, one important detail was not clearly specified: once the issue was fixed and the workflows were re-enabled, the leads that had not been synchronized during the outage would automatically be retrieved and processed by Pabbly.

Since we were not aware of this, we started manually recovering the missing leads from Meta and adding them to our Google Sheets. When we later re-enabled the workflows, Pabbly automatically processed those pending leads as well, which resulted in duplicates of the leads we had already added manually.

Had we known that the pending leads would be automatically recovered after re-enabling the workflows, we would simply have waited for the synchronization instead of spending several hours manually recovering them.

Regarding the tasks consumed during the technical issue, unfortunately I cannot quantify exactly how many tasks were unnecessarily used. There were many workflows involved and multiple repeated executions during the incident.

Since you mentioned that your team can verify this, could you please check the abnormal task consumption on our account during the affected period and restore the tasks that were consumed because of the issue?

Thank you.

Hi,
after carefully reviewing the entire conversation, I realized that you had actually already specified that the leads not received during the issue would be processed automatically once the problem was fixed.

I apologize for my previous message. That information escaped me in the confusion of the day, while we were dealing with the issue across multiple workflows, duplicate executions and lead management.

At the moment, the workflows appear to be working correctly and the pending leads are being processed as expected.

Thank you for your support and for helping us resolve the issue.

We will continue monitoring the workflows to make sure everything remains stable.

Hello Salvo,

Thank you for reviewing the conversation and finding the information about the pending lead being processed once the issue is resolved.

We have reset more tasks than the actual consumption on your account due to the issue; please check at your end now.