adwhispr
MetaError reference

Too Many API Calls: User request limit reached (Meta, code 17)

What Meta's 'User request limit reached' or 'Too Many API Calls' error (code 17, code 613) means when you change many campaigns quickly through AdWhispr, why retrying makes it worse, and how long to wait.

Whose side it is on
A temporary limit Meta applies to the ad account. Wait, then run the change once.
What you see
(#17) User request limit reached (code 17, subcode 2446079)

Updated September 7, 2026 · 1 min read

What this error means

Meta rate-limits an ad account that receives too many changes in a short time, for example ten launches followed by ten budget updates. While the limit is on, every write to that ad account fails with this message, whatever tool sends it. On the current access tier the block lasts about five minutes.

Whose side it is on

Meta's limit on the ad account. It is temporary.

How to fix it

  1. Wait about five minutes without retrying. Every retry during the block extends it.
  2. Then run the change once.
  3. If you have a long list of changes, make them in a few batches with a pause between them.

Relaunch

After the wait, run the same request again. Changes that failed during the block were not applied, so repeat them.

Frequently asked questions

Did my changes go through?

No. A change that hit this error was not applied. Ask the chat to list the campaigns or read the account state to confirm what exists, then repeat what is missing.

Does this affect my other ad accounts?

The limit is per ad account. Other accounts keep working.

Related pages