Error while hydrating data from Facebook Lead Ads: The app returned "Unsupported get request. Object with ID '1xxxxx' does not exist, cannot be loaded due to missing permissions, or does not support this operation. Please read the Graph API...
Best answer by SamBBest answer by SamB
Hi everyone! 👋
Just following up here to confirm that these errors should now be resolved. For anyone that missed it here’s the latest update from the incident page for details:
Resolved - This incident, which previously resulted in errors in Facebook Lead Ads triggers, has now been resolved.
Meta has confirmed that a fix has been released and our Engineers have started replayed the runs. Any remaining errors will be replayed and all leads should be processed successfully.
If you have any questions or need additional clarification, you can contact our Support team at https://zapier.com/help
We appreciate your patience while we worked on resolving this issue. Thank you.
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 @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.
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! 🙂
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! 🤞
Just following up here to confirm that these errors should now be resolved. For anyone that missed it here’s the latest update from the incident page for details:
Resolved - This incident, which previously resulted in errors in Facebook Lead Ads triggers, has now been resolved.
Meta has confirmed that a fix has been released and our Engineers have started replayed the runs. Any remaining errors will be replayed and all leads should be processed successfully.
If you have any questions or need additional clarification, you can contact our Support team at https://zapier.com/help
We appreciate your patience while we worked on resolving this issue. Thank you.