Facebook Lead Ads workflows not triggering automatically

Hello,

I am experiencing a new issue with workflows using Facebook Lead Ads as the trigger..

The workflows are enabled and work correctly when tested manually. However, when a new real lead is submitted through Meta, the workflow does not start automatically.

I have checked multiple workflows, lead forms and Facebook Pages and the behavior is the same: the lead is correctly recorded on Meta, but Pabbly does not automatically capture it, so the subsequent workflow steps are not executed.

Therefore, the issue appears to be related to the Facebook Lead Ads trigger again rather than to a specific workflow.

A few days ago we experienced the previous Facebook Lead Ads trigger issue, which was subsequently resolved by your technical team.

After the fix, our workflows started working correctly again and the pending leads were also successfully processed.

Now, however, we appear to be experiencing a new issue: new leads are no longer automatically triggering the workflows.

Could you please urgently check our account and the Facebook Lead Ads trigger?

This is important for us because we use these workflows to automatically manage Meta leads across multiple locations.

Thank you.

Hello Salvo,

Thank you for the detailed information.

We have already shared the “Bologna Fiera Gestione StoreFit - 19.90” workflow with our technical team for further investigation of the Facebook Lead Ads trigger issue.

If you are experiencing the same issue with any other workflows, please share the workflow names or URLs with us as well. We will provide those details to the technical team so they can check the affected workflows together.

Hello,

thank you for the update.

Unfortunately, the issue is not limited to the “Bologna Fiera Gestione StoreFit - 19.90” workflow.

I am experiencing the same behavior across multiple workflows that use Facebook Lead Ads as the trigger. New leads are correctly received in Meta, but the corresponding Pabbly workflows do not start automatically.

I can provide you with additional affected workflow names and URLs so your technical team can investigate them together.

Since we manage a large number of Facebook Lead Ads workflows for different StoreFit locations, could you also please check whether this may be a broader issue affecting the Facebook Lead Ads trigger on our account rather than individual workflows?

Thank you.

Here are three additional examples of workflows where I am experiencing the same issue:

https://connect.pabbly.com/v2/app/workflow/mapping/IjU3NjcwNTZkMDYzZjA0MzI1MjY4NTUzMjUxMzAi_pc

https://connect.pabbly.com/v2/app/workflow/mapping/IjU3NjcwNTY5MDYzMjA0MzQ1MjZjNTUzNDUxMzYi_pc

https://connect.pabbly.com/v2/app/workflow/mapping/IjU3NjcwNTZjMDYzZjA0MzA1MjZjNTUzYzUxM2Ei_pc

These are only a few examples. Unfortunately, I am experiencing the same behavior on many more workflows using Facebook Lead Ads as the trigger.

New leads are correctly received by Meta, but they do not automatically trigger the corresponding workflows in Pabbly.

I would also like to mention that I recently migrated to the new Pabbly interface. Could this issue possibly be related to the migration to the new interface or to something that changed in the workflows during the migration?

Please ask your technical team to check this possibility as well, since the problem appears to affect a significant number of workflows on my account.

Thank you for your support.

Hello,

Thank you for sharing the additional workflow examples and the detailed information.

We have already forwarded the Facebook Lead Ads trigger issue to our technical team for investigation. We have also added the additional details you shared regarding the migration to the new Pabbly interface/builder, as this may be relevant to the issue.

The technical team will review the additional workflows and check whether the behavior is related to the migration or any changes made during the transition.

We will get back to you once we have an update from the team.

Thank you for your patience and cooperation.

Hello,

thank you for the update.

While your technical team is investigating the issue, I would also like to clarify one important point regarding the leads that are currently not being processed by the affected workflows.

Once the issue is fixed, will the leads that were not processed during this period be automatically retrieved and processed by Pabbly, as happened after the previous Facebook Lead Ads trigger issue?

Or should I manually recover these leads from Meta Business Suite and add them to our Google Sheets?

I would prefer to wait if Pabbly will automatically process the pending leads after the fix, in order to avoid creating duplicates by manually adding leads that may later be recovered automatically.

Could you please confirm how I should proceed?

Thank you.

Hello,

Thank you for reaching out and for clarifying your concern.

We understand that you would prefer not to manually add the affected leads to your Google Sheets if there is a possibility that Pabbly may retrieve and process them automatically after the issue is resolved, as this could potentially result in duplicate entries.

Since today is Sunday, our technical team is currently unavailable to verify how the pending leads will be handled in this particular case. The team will check this tomorrow, once normal operations resume, and confirm whether the leads that were missed during the affected period can be retrieved and processed automatically.

We therefore recommend waiting until we receive confirmation from the technical team before manually adding the affected leads, so that we can avoid any possibility of duplicate processing.

We will update you once the team has checked this.

Hello Salvo,

Thank you for your patience.

Our technical team has completed the investigation and confirmed that the Facebook Lead Ads trigger issue was on our side and was not related to the migration to the new Pabbly builder. The issue has now been fixed.

The leads that were missed during the affected period have also been delivered and should now be visible in Task History.

Please note the following:

• If you manually added any affected leads to Google Sheets or Brevo since September 21, please check those records for possible duplicates.

• For leads from the form used before switching to the Reggio Emilia form, you will need to export those leads from the Meta Leads Center.

• We have also identified the following disabled Facebook Lead Ads workflows that still have missed leads from the September 21 issue:

  1. 1396489: IjU3NjUwNTZlMDYzZjA0MzI1MjY4NTUzYzUxM2Ii_pc

  2. 1822417: IjU3NjUwNTY1MDYzNDA0MzY1MjY4NTUzNTUxMzUi_pc

  3. 2668030: IjU3NjYwNTZiMDYzMDA0M2M1MjZjNTUzNzUxMzIi_pc

  4. 2745290: IjU3NjYwNTZhMDYzMjA0MzE1MjZlNTUzZDUxMzIi_pc

If you need the missed leads from any of these workflows to be captured, please enable the respective workflows and let us know. We will then process the available missed leads for those workflows.

Please check your Task History and connected applications, and let us know if you notice any missing or duplicate leads.

Hello Salvo,

Just following up regarding our previous update on the Facebook Lead Ads trigger issue.

We have already confirmed that the issue was fixed from our end and that the missed leads were delivered for the affected active workflows.

For the four disabled workflows listed below, please let us know whether you would like us to process their missed leads as well:

1. 1396489: IjU3NjUwNTZlMDYzZjA0MjY4NTUzYzUxM2Ii_pc

2. 1822417: IjU3NjUwNTY1MDYzNDA0MzY1MjY4NTUzNTUxMzUi_pc

3. 2668030: IjU3NjYwNTZiMDYzMDA0M2M1MjZjNTUzNzUxMzIi_pc

4. 2745290: IjU3NjYwNTZhMDYzMjA0MzE1MjZlNTUzZDUxMzIi_pc

If you have already enabled any of these workflows, please let us know which ones. We can then proceed with the available missed leads accordingly.

Also, please check your Task History, Google Sheets, and Brevo for any duplicate entries if you manually added leads after September 21.

Hello,

thank you for the follow-up and for your support.

The four disabled workflows you mentioned are not currently needed, so there is no need to process the missed leads for those workflows.

As for the other active workflows, everything now appears to be working correctly and the leads are being processed as expected.

We will continue to monitor the situation and will let you know if we experience any further issues.

Thank you again for your assistance.

Best regards,
Salvo

Hello Salvo,

Thank you for the confirmation and for the update.

We’re glad to know that the active workflows are now processing the leads correctly and that everything is working as expected.

We have noted that the four disabled workflows are not required, so we will not proceed with processing their missed leads.

Please continue monitoring the workflows, and feel free to reach out if you notice any further issues.