Get Solutions

Hi! :) I submitted my Figma plugin Tokenry about 17 days ago, and it’s still in review. Just wanted to check if this is expected, or if there might be something wrong on my end. Plugin link:https://www.figma.com/community/plugin/1612136415712068154/tokenry It’s a design token generator that helps create variables, semantic tokens, and dev-ready structures in Figma. I haven’t received any feedback or requests for changes so far, so I’m a bit unsure if:  it’s just a long queue or if something might be blocking the review  Has anyone experienced similar wait times recently? And is there anything I should do (or check) while waiting? Really appreciate any insight 🙏

Hi everyone,I recently submitted my Figma plugin “Designer/Developer Toolkit” for review and wanted to ask about typical approval timelines.It’s a productivity-focused plugin that helps with:Structured layout generation Design consistency Reducing repetitive manual work Bridging design → development workflowsThe plugin was submitted around ~2–3 weeks ago (on March 19th), and I can see it’s still under review.Would appreciate insights on:Typical approval time (days / weeks?) Whether delays are common If there’s anything I should double-check while waitingThanks

I have been experiencing unusual behavior in Figma for several days. When I use Spacebar + mouse to pan, the canvas moves unpredictably in different directions while the spacebar is pressed. Refreshing Figma temporarily resolves the issue, but the glitch reoccurs frequently. I am using Figma Web.

Hello. There is a loading icon that is appearing and won’t go away/I am unable to view the result. I’ve tried all the steps but nothing has seemed to work. Steps i’ve tried:Duplicating the file Refresh Opening in a browser window (instead of the app) Restarted the app and laptop too Also, my websockets also work. Tried opening through my personal laptop (Windows) and still got the same issue. (I use Mac for work purposes but get the same issue) I checked all queries regarding this and tried all methods. Nothing is working. Prompting that I’m only seeing a loading window and providing it with a screenshotI’ve also confirmed that no errors are showing. 

QUUERO REEMBOLSO DA MINHA COMPRA QUE FOI FEITO HOJE SEM MINHA PERMISSAOQUERO QUE CANCELEM A ASSINATURA SPOR GENTILEZA 

I have paid for more credits as my allowance will reset on 16 April. Yet nothing has happened - cannot ‘make’ anything new.Tried to get a response from them and nothing.Suggestions?

[image redacted by moderator to remove personal information]Hello everyone!I filled out the educational subscription form on the Figma website incorrectly and can't resubmit it.I can't upgrade my plan in Figma—they're asking me to sign up for a professional subscription. I'm a student taking courses at an IT school. Perhaps you were in a hurry and didn't fill out the form carefully. If you've encountered this issue, I'd be happy to hear from you.

The error message shown to me by Figma Make is: "Couldn't load Make. Try checking your network connection or refreshing the page. (M2)"I have tried checking my network, VPN and DNS settings, switching to different browsers to access Figma Make, and logging into it on different computers, yet the issue still persists.However, my teammates in the same team can use it normally, and we are all under the same network environment. So I suspect that the problem might be related to my account. Could you please help me resolve this issue? Thank you so much!

Hi,I don’t know if I’m the only one with this problem. I have the slot. I configure it, etc. everything awesome.I take the instance, try to use it.Add an instance of the component that I had selected as the preferred one.Now, it breaks my Fill for width and height for the component and the component doesn’t fill the slot area!Now, I know it has to be changed to fill but weren’t slots supposed to be automatic? So that whatever is put there, it behaves like it should?WTF?Another BROKEN FEATURE… OMFG. 

HI I get subscription in December, but it charged until now. And I thought I cancelled the subscription in Febuary and delted all my account information. But why they charge me over $ 80. I need to get refund my money. Please check it as soon as possible. 

How to fix the “Live preview failed” issue in Figma Make? I did the troubleshoot and immediate fixes available in the internet like: refreshing the page, duplicating the page, opening in different browsers. It is still working properly on March 13, 2026 but the problem started on March 16, 2026

need a way to purchase additonal credit ..pls help!

Hi Figma team,I submitted my plugin DesignOPS (ID: 1603703295257406223) for review approximately 10 days ago and haven't received any updates yet — no approval, no rejection, no feedback.The plugin is a design audit and library cleanup tool:Scans Figma files for missing styles, broken tokens, orphaned components, grid violations Offers one-click autofix and bulk replace across libraries Uses networkAccess for user authentication and library resolution via our own backend (api.design-ops.pro) Requires a free account (email registration, done inside the plugin) Has Free and PRO ($8/mo) plans Bilingual UI (English & Russian) I've reviewed the plugin review guidelines thoroughly and believe the plugin meets all requirements. Privacy policy, terms of service,

Dear Support Team,I would like to request your assistance in prioritizing the following billing support case:Case ID: 1814809As the deadline is approaching, this matter is time-sensitive and requires urgent attention to avoid any impact on our operations.We would greatly appreciate your prompt support and update on this case.Please let us know if any additional information is required.Best regards,

The generate_figma_design tool — documented as "Claude Code only, remote only" in Figma's developer docs(https://developers.figma.com/docs/figma-mcp-server/tools-and-prompts/) — is not available in my Claude Code session despite the Code to Canvas feature being officially announced on Feb 17, 2026. My setup:  - Figma MCP remote server is connected and working (all other tools like get_design_context, get_screenshot, whoami etc. work fine)  - Full seat on a Pro tier Figma plan  - Figma desktop app is running  - Claude connector browser shows Figma connector version 1.0.3 The tool simply isn't exposed in the tool list. Is this a version/rollout issue on the connector side, or are there additional requirements to access this tool?

I’m having some problems with Figma slots as it seems to not fully support nested component Boolean properties.The situation is that I have componentA with slot and componentB with slot, then nest componentA instance inside componentB’s slot. The issues happen when I try to work with the elements inside the slot of componentA instance. The layer panel looks like below.  Here are the issues:Boolean property doesn’t support all elements inside instance slots. Only the component instances support it, the texts & frame don’t. Value of boolean properties doesn’t effect the elements. E.g. when the value is false, the element is not hidden. Also, detaching property from the elements doesn’t work. Boolean properties are listed for Compon

I submitted my plugin for review on March 8th, and as of today (March 27th) I still haven't received any feedback from the Figma team. No approval, rejection, or requests for changes.That's over 20 days of waiting, while the submission form indicated a turnaround of 5-10 business days.Could anyone share how long the review process is currently taking? Is this wait time normal right now, or should I follow up somewhere specific?

Hi Figma Team,I am reporting a severe bug with Figma Make that resulted in a completely hallucinated design and the unfair loss of ~250 AI credits on my Professional plan.I attempted to generate a specific dashboard ("v3 / dashboard") using my "Caregiver Web Portal" design system. Despite attaching my local library and providing explicit rules in Guidelines.md, the AI failed completely.The Issues: Ignored Libraries & Guidelines: The tool completely ignored my attached components and explicit styling rules, hallucinating an entirely different and unusable UI. Server Crashes: I hit multiple "Model is overloaded" errors and endless Vite preview engine spinners. Massive Credit Drain: One single incorrect generation cost me 172 credits. In total, I have lost nearly 250 credits to these bugs and server failures.

Can you please help check the status of it?

I’ve submitted a couple of plugins, but they’re still under review. One of them has been waiting for about a month:https://www.figma.com/community/plugin/1615271839569985921/ https://www.figma.com/community/plugin/1620738014327336695/I saw that the review process usually takes around 5-10 business days, so I’m wondering whether something may have gone wrong. I haven’t received any confirmation email after submission, or any other update since then.Does anyone know how I can check their status or whether they might be stuck in review?

Hi everyone, I submitted my plugin (ID: 1613871404512183792) a couple of weeks ago, and since then, my page has just been showing the message: 'Only you can see it while your plugin is in review.’ I haven't received a single email or status update. Is it common for the review process to take this long without any communication? Has anyone else experienced a similar delay, or does anyone know how long it usually takes to get the review results in cases like this? I’d really appreciate any pointers or help with this. Thanks in advance!

I submitted my Figma plugin, Grotto Slice, for review on March 14th. The website states a 5-10 business day approval, but it's now been over three weeks with no response - no approval, no rejection, and no requests for changes or additional information.At this point I'm unsure what to expect or if there's something I should be doing differently. Is anyone else experiencing similar wait times, or is there a better way to check on the status of a submission?Many of my clients are waiting on this plugin being approved, and I would love to launch for them shortly. Thanks.

When I switch variables, the component instance resets to the default item. I hope that when switching variables, only the component size is changed, and the icons and text called by the component instance are retained. How should I adjust this? However, I found that if the component instance is separated, the component instance can be retained when switching variables. Has anyone else encountered the same problem? And are there any known solutions?Thank you.

Perfect — I understand the exact style you want (simple ovals + arrows like your sample). Below are DFD Level 0, Level 1, and Level 2 tailored to your project, in the same clean format.---📊 6.2.1 Data Flow Diagram 0 LevelCT/MRI Image + Clinical Data  →   (Kidney Tumor Detection System)   →   Tumor Result + Diet Plan🧾 CaptionFig 6.2.1 DFD 0 Level---📊 6.2.2 Data Flow Diagram 1 LevelInput Data     ↓(Data Collection & Preprocessing)     ↓Processed Data     ↓(Image Segmentation)     ↓Tumor Features     ↓(Clinical Data Processing)     ↓Patient Features     ↓(Diet Recommendation)     ↓Final Output (Tumor Result + Diet Plan)🧾 CaptionFig 6.2.2 DFD 1 Level---📊 6.2.3 Data Flow Diagram 2 Level(More detailed — this gives you extra marks 🔥)Input Data     ↓(Data Cleaning &a

Prototypes embedded in Figma Slides no longer allow full vertical scrolling during presentation, even though vertical scrolling works correctly when the prototype is played directly. This appears to be a regression, as the same slides and prototypes worked previously. Whats happening: In the past, I’ve been able to embed interactive prototypes into Figma Slides and present them with full vertical scrolling enabled.Today, I created a new slide deck and added a prototype, but the vertical canvas scroll does not work as expected during slide presentation, despite working correctly when the prototype is played on its own.After noticing this, I went back and checked older slide decks where this behavior previously worked, and I’m now seeing the same scrolling issue there as well. Current behaviour for me:Scrolling only works within the initial height that was load