Meta ads error
Error 32: Page request limit reached
The user or app whose token is used has reached the rate limit for Pages API calls (calls made with a user access token).
(#32) Page request limit reachedCommon causes
- Too many Page calls with the same user token in a short time.
How to fix it
- Wait before calling the Page again.
- Check the X-Business-Use-Case-Usage header for when calls can resume.
How Kapao handles it
Kapao queues its calls to Meta with a pause between them. If Meta still answers with a rate limit while Kapao publishes to several markets, Kapao waits 30 seconds, tries that ad once more, and stops the run if the limit is hit again, because more calls only keep the block going.
Questions
- What does Meta error 32 mean?
- The user or app whose token is used has reached the rate limit for Pages API calls (calls made with a user access token).
- How do I fix Meta error 32?
- Wait before calling the Page again. Check the X-Business-Use-Case-Usage header for when calls can resume.
- Will error 32 go away if I just try again?
- Not right away. Wait before trying again: more calls during a limit or block usually make it last longer.
- Does Kapao handle error 32?
- Kapao queues its calls to Meta with a pause between them. If Meta still answers with a rate limit while Kapao publishes to several markets, Kapao waits 30 seconds, tries that ad once more, and stops the run if the limit is hit again, because more calls only keep the block going.
Related errors
Source: Meta for Developers: Graph API Rate Limits, checked November 10, 2026
Kapao is an independent tool, not a Meta product. Meta can change its error codes and messages without notice; check the source if something does not match.