Please help me understand what the problem is.
I’ve been using Make for two months and I have a scenario that transfers leads from Facebook Ads to my CRM. From time to time I noticed some errors in the logs, but the scenario kept running and the leads were transferred consistently.
This week, however, whenever the error occurs, the scenario gets turned off and leads are no longer delivered. The error description is “very informative” – Scenario was deactivated by Make because of reason: (, ).
In a neighboring thread I found information that there were issues with the Facebook API on Facebook’s side, but supposedly they have already been resolved.
When I reconnect the Facebook account, no errors appear during the reconnection. But as soon as the scenario runs again, the same error occurs and the scenario stops again and adain.
What is causing this problem and how can it be fixed?
The scenario regularly stops working, and I have to constantly check and restart it. This is very inconvenient, considering that Make was used to automate the process of transferring leads to CRM.
Sorry for the trouble this has caused. Our team is already looking into it and is in touch with the Meta team regarding this issue. We’ll make sure to keep you updated as soon as we have news to share.
In the meantime, could you please confirm whether you’re using your own OAuth app for the Facebook connection, or if you’re relying on Make’s default OAuth connection?
You can check this in your Facebook Developer settings, specifically under Upgrade API version (see screenshot below for reference). It will show the API version your app is calling.
Thank you so much for your patience and understanding.
Hello everyone, thank you very much for your patience.
Our dev team is currently reviewing this and requires some additional time to complete the investigation. We’ll make sure to keep you updated on any progress in this thread.
If you’d prefer to receive updates in your email inbox, please open a support ticket with our Customer Care team, who will be happy to keep you posted.
We’re very sorry for the frustration and disruption this may be causing. Thank you very much for your understanding
I’m just stepping in to let you know that this issue has been fixed and the update is now live.
Please feel free to test it on your end and let us know if everything works as expected.
Once again, thank you so much for your patience and understanding as we worked to resolve this