Getting 'Error while hydrating data from Facebook Lead Ads: The app returned "Unsupported get request. Object with ID...' errors

I’m seeing the same issue, but I could be facebook related as when I got into Ads manager and try to download the CSV file of todays leads its showing blank yet there are 3 leads showing in ads manager  

Hi - I’m seeing the same issue with the same error message as the first post

We're experiencing the same issue.

Same issue here since 4 GMT. I’ve checked all the permission and all seems fine on Meta.

Same here since 7 AM CET. 

Same here since 4 gmt - hoping it was some sort of update that may be fixed soon?!

Hi @AndrewEleven, @m19rtg, @LAH, @G2G, @Mattia Colleoni, @Weegree and @Hbug 👋

Facebook Lead Ads is experiencing issues on its platform, which is causing these errors to surface in your Zaps. We’ve opened an incident for this here: Facebook Lead Ads: Error with hydrating data and permissions. And we’ve also got a bug report open for this issue which you’ve all been added to. This will ensure that you all receive an email notification the moment it’s been resolved.

In the meantime, you can find out more details the incident page here: https://status.zapier.com/incidents/s3gw554r1rdr. Click the Subscribe To Updates button on that incident page to be kept informed of any progress updates shared there.

Thanks in advance for everyone’s patience on this. The team are working closely with Meta to resolve things as quickly as possible and we’ll share further updates as soon as we can. 

hi, We're experiencing the same issue.

thank you

Hello. We are experiencing this too. We’ve gotten about 10-12 errors since last night… Starting around 11:30pm EST.

Same here. Tried to download in ads manager but it’s showing blank.

 Thanks for reaching out here @osnetwireless, @Port35 and @JD RNT. I’m so sorry to hear that you’re all being affected by this as well. 

You’ve all been added to the bug report so we’ll definitely be in touch over email once it’s sorted. In the meantime please subscribe to updates on the incident page here to follow along with any updates on progress. Thanks! 🙂

We have been facing the same issue,  Please add me to the bug report too @SamB 

Thanks

Same issue on our end, please add me to the bug report also! @SamB
 

Thank you!

Danielle

Same issue - please add me to the bug report also! @SamB
 

Thank you - is there any updates at all on your end on this/when a fix may be released?

Dinty

Hi @GHV_Adv, @Danielle B and @dintyandrews 👋

You’ve all been added to the bug report as well now, so you can expect a notification from us once it’s confirm that it’s been fixed. 

Where things currently stand is that Meta have have shipped a fix for this which as reduced the numbers of errors occurring, but they’ve not entirely subsided. We will continue to monitor the situation and work with Meta to ensure this is fully resolved for everyone’s Zaps. And we’ll follow up with further updates in the incident page.

Thanks again for everyone’s continued patience here. Hopefully this will be fully resolved soon! 🤞

Same issue - please add me to the bug report also! @SamB 
 

Thank you!