Magicul Figma Backup uses the official Figma API. If Figma returns a rate-limit response, we pause affected backups until Figma says requests can be retried.
Errors you might see
Figma is currently rate limiting this backup.
Figma API rate limited.
Figma returned a 429 response.
Retry is temporarily disabled for this file, team, or account.
Why this happens
Figma applies API limits by account and request type. A backup can make several different kinds of Figma API requests, so one endpoint can still be paused even when another endpoint works.
Rate limits are more likely when many files are backed up at once, a large team import is running, the same Figma account is used by multiple tools, or the connected Figma account has View-only or Collab access instead of a Dev or Full seat.
What to do
Make sure the connected Figma account has a Dev or Full seat for the files or team being backed up (see: https://help.magicul.io/en/articles/15292806-which-figma-seat-do-i-need-for-figma-backup)
If your seat was upgraded, reconnect Figma in Magicul so the new permissions are used.
If a large team import is running, let the current queue drain before starting another import.
Check your Figma plan and seat
If rate limits keep coming back, confirm that the connected Figma account is not on View-only, Collab, or Starter/free access.
Open Figma's seat and upgrade page and check the plan and seat for the team or organization that owns the files. Magicul backups need a paid Figma plan with a Dev or Full seat.
Read more about the required Figma seat in our Figma seat article. Figma also documents its API policy on the official rate-limit page.