Summary
Watch Leads (Facebook Lead Ads) scenario starts failing intermittently on every lead with HTTP 400 / GraphMethodException 100. Error rotates the lead ID each time, indicating individual lead GETs fail, not the trigger itself.
Error
[400] The HTTP request that was sent to the server has invalid syntax.
Details:
Unsupported get request. Object with ID ‘1657463498634256’ 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)
The ID changes per failure (next run: 4487725048137664, etc.). Each is a distinct lead record.
What I’ve verified is NOT the issue
- Token: Long-standing connection, was working for over a year
- Page-level Leads Access (business.facebook.com/settings/leads-access): correctly assigned, I’m a Page admin
- leads_retrieval permission: granted on the connection
- Lead form: active, recently received leads in Lead Center
- 90-day window: failing leads are within 24h (test leads via Lead Ads Testing Tool also fail)
- Direct Graph API call: same
GET /{lead-id}via Graph API Explorer with the same token succeeds 200 and returns lead data
So the token + scopes + page permissions are fine. Make’s internal call to Graph API is what fails.
Reproduction
- Set up a Facebook Lead Ads “Watch Leads” trigger on any Page with active form
- Receive a lead (or generate via Lead Ads Testing Tool)
- Scenario runs → 100 error on lead GET, ID rotates each retry
Existing thread
Facebook API error 400 (100, GraphMethodException) — same symptom reported around late 2025. No resolution.
Ask
- Is this a known regression in the Facebook Lead Ads module?
- Any ETA or workaround beyond migrating off Make?
- Status page link if there’s an active incident — couldn’t find one at status.make.com
This is blocking lead capture for production traffic.