Figma limits how often its API can be called. If you see a message saying access has been paused, that limit comes from Figma and applies to your token. Nothing on your site is broken.
Why it happens
Figma meters API usage per token and weights each call by cost. Reading files, reading nodes and rendering images are its most expensive calls, and those are exactly the ones used when pulling a design. Pulling many frames in a short burst can use up the allowance.
What still works
Everything already in your library. NibWP caches each pulled frame, so converting a design you have already pulled needs no calls to Figma at all. Only pulling new frames has to wait.
How to get going again
- 1Wait for the period shown in the message to pass.
- 2Or use a token from a different Figma account. The limit follows the token, not your site.
- 3Check the seat type: View and Collab seats get a far smaller allowance than Dev and Full seats.
- 4Higher plans raise the allowance on the calls NibWP uses most.
Avoiding it
Pull what you need rather than an entire team at once, and use Re-sync library only when designs have actually changed. NibWP already caches responses and downloads only the images a frame really uses.