Facebook Lead Ads Trigger Stopped Working After 8th December for Specific Workflows

[ChrisJW94]

Your Workflow URL

https://connect.pabbly.com/workflow/mapping/IjU3NjcwNTZkMDYzNjA0MzI1MjZiNTUzNTUxMzQi_pc

Your Task History ID

IjU3NjUwNTY1MDYzNjA0MzY1MjZjNTUzNDUxMzY1MTY0NTQzMjBmMzQi_pc

Consent to Access & Modify

I authorize Pabbly Support to log in to my account and make changes to the specified workflow for troubleshooting.

I’m experiencing an issue with one of my workflows and wanted to check if you can help investigate.

I have multiple workflows set up to send Facebook Lead Ads leads into Google Sheets. These have been running fine historically. However, one specific workflow for an Invisalign lead form has completely stopped triggering since 8th December.

We have received plenty of new leads via Facebook since then, but the workflow history only shows executions up until 8th December, with nothing recorded after that date.

What’s confusing is that:

• Another workflow for the same client is still working perfectly
• Both workflows use the same Facebook connection
• Other workflows using this same Facebook connection for different clients are also working fine
• This issue happened on the same date (8th December) for another client as well, with a different lead form

Because of this, it doesn’t seem to be a Facebook connection issue. It feels more specific to the lead form or how the trigger is picking up new leads for these particular workflows.

I haven’t come across this behaviour before, so I wanted to see if there’s anything on your end that could explain why the trigger stopped firing from that date onwards.

Happy to provide workflow IDs, lead form IDs, or screenshots if needed.

Thanks in advance for your help.

 

[ArshilAhmad]

Hi @ChrisJW94,

We sincerely apologize for the inconvenience caused. We experienced a server downtime that affected multiple polling-based services.

Downtime (UTC):
• Dec 8, 2025 — 14:58 UTC to Dec 8, 2025 — 23:35 UTC
• Dec 9, 2025 — 02:30 UTC to Dec 9, 2025 — 04:35 UTC

Impacted Services:
• Scheduler
• Polling
• Delay
• Auto-Retry

If your workflow or trigger uses any polling-based application—or depends on the Scheduler or Delay module—it may not have executed during the above windows. All services are now fully restored and functioning normally.
The Facebook Lead Ads: New Lead trigger step is based on polling. We suggest cloning the workflows where you encountered the issue and checking if the new cloned workflows are being triggered.

If the cloned workflows are not triggered either, please let us know.

Thanks & Regards,
Arshil Ahmad
Customer Support Associate
Pabbly.com
Rate your support

 

[ChrisJW94]

Hi Arshil,

Thanks for the explanation. Unfortunately, we are still experiencing the same issue today.

Since yesterday, we have received four leads, but there is nothing showing in the workflow history. We sent a test lead yesterday and again today, and both tests came through without any issues. However, the actual leads do not appear to be passing through the workflow.

We also have another workflow connected to the same Facebook account, using a different campaign and lead form, and that workflow is working perfectly.

This is the workflow we are having issues with:
https://connect.pabbly.com/workflow/mapping/IjU3NjcwNTZkMDYzNjA0MzI1MjZiNTUzNTUxMzQi_pc

Thanks,
Chris

 

[Preeti Paryani]

Hey @ChrisJW94,

Could you please share any unique details of the concerned leads? So we can review the issue.

we have received four leads, but there is nothing showing in the workflow history.

 

[ChrisJW94]

Hi Preeti, we've had another 3 leads through since yesterday and still nothing. What sort of details do you need?

 

[Preeti Paryani]

Hi @ChrisJW94,

Upon checking, it appears that the workflow shared in your query has been moved to the Trash folder, as shown in the attached image. Since the workflow is currently in the trash and inactive, no data has been captured or executed.

Please restore the workflow from the Trash folder and test it again. Let us know if you face any issues after restoring it.