Hey everyone. Having some trouble with lead routing this evening. All 7 of my scenarios threw the same error at the same time and are no longer receiving and routing leads. I have tried reestablishing the connection multiple times and and still getting the same error message. I did nothing, just checked my email and saw a mile long list of Stop Sign emails…
Scenario was deactivated by Make Scenario has encountered an error while being processed. Fix the error or clear the queue. The reason is: [400] The HTTP request that was sent to the server has invalid syntax. Details:
Unsupported get request. Object with ID
"1333054198734676’ does not exist, cannot be loaded due to missing permissions, or does not support this operation. Please read the Graph API documentation at
I think this is gonna be the last straw for me, I’m moving everything over to Zapier tonight… absolutely sucks but this service is too unreliable for how large my operation has become… really good for testing things out though
Same here… each automation is failing one by one as leads are trying to filter in, have over 40ish active automations in make all using lead form trigger and they are all failing. I’ve tried reconnecting, relinking, double checking all permissions, pretty sure it is a make.com issue at this point. Huge disruption unfortunately.
I send a ticket to make and this is thier respons
Hi Shir,
Apologies for the inconvenience.
Our development team reviewed the behaviour, and this appears to be a known recurring issue on Meta’s side. Based on previous cases, the same error has occurred for other users across platforms such as Make and other automation tools, and the resolution has consistently been handled by Meta from their end.
From the past trend, this issue has not been caused by the Make module itself but rather by Meta’s API/customer-side setup, and it has always been resolved once Meta addressed the underlying issue.
As an initial step, we would recommend trying the workaround mentioned here, as it has helped in similar cases previously: Community workaround reference
We also found similar discussions reported directly in Meta’s developer community, which indicates this is an ongoing issue acknowledged on their side:
Since this has historically been resolved by Meta, we would strongly recommend also reaching out to Meta support regarding this issue.
Meanwhile, our team can continue monitoring from our side as well, and we have also reached out to Meta from our end, but based on prior cases, the final resolution has always come from Meta’s side.
Let me know if you have any more questions about this issue.
Should you have another topic to raise, please create a new ticket so that we can answer you more efficiently.
You can always check your logged tickets in our Customer Portal.
I am having the exact same issue, I’ve tried reconnecting and disconnecting every possible area and relinking every possible thing I can. Every automation is failing one by one as new leads come in on lead form.
Hello, It appears to be an issue on Make’s side. Since this morning, the automations have been stopping whenever a new lead comes in.
You guys have the same problem?
**
RuntimeError**
[400] The HTTP request that was sent to the server has invalid syntax.
Details:
Unsupported get request. Object with ID ‘2694120777626595’ does not exist, cannot be loaded due to missing permissions, or does not support this operation. Please read the Graph API documentation at https://developers.facebook.com/docs/graph-api (100, GraphMethodException)
all my scenarios stopped