Skip to main content
Solved

Can I complain the terrible performance about my Figma Make that made me mad and ask back 1000 credits which had been run out for nothing?

  • May 29, 2026
  • 7 replies
  • 99 views
Deagle

Hi, Dear administrators or technical support experts,

I had a bad experience when I ask my Figma Make to figure out a database schema of math knowledge point of junior high, actually it turned out to be a big risk for me to challenge Figma Make’s abilities for AI system connection and content offering. Here are the records of what I have met:
1. I downloaded the document of knowledge point and translated it into .md format. 
2. I fed the .md file to Figma who had convinced me to provide materials.
3. Then the terrible experience began, Figma told me it would and could process the .md file and turn the corresponding schema result back quickly, the responses were always confident with missions always failed, again and again. Only with my impatient questioning, would Figma give me a reply, something like “OK, I will do it immediately, it will soon be finished”. And this experience had lasted nearly for 8 hours!
4. Unfortunately, my AI credits had been run out accordingly with every ineffective conversation, almost from the full value of 3000 to 2120 while nothing finished. And Figma had never given me any illustration or explanation about it until I changed the mission to another, I was depressed at those moments.
5. The final result of the math knowledge point schema is very simple, without the promised knowledge layers according to the table structure, I have to do the left works aftermath manually, it is hard and terrible without AI’s strong support.
6. Moreover, I have asked Figma to develop the frontend UI pages to present the result of data content imported into my database, it still failed again and again and the page remains empty until now. 500 more AI credits has been used without a sound performance.

Please you guys check out and evaluate what the records I am offering and the 1000 AI credits back to my account. I am happy to provide the screenshot pictures during the all processes if you guys ask.

Thanks.
Best Regards

Best answer by Gayani_S

Hey ​@Deagle, thanks for the update! 

One thing I want to make sure doesn't get lost: this reply came through here on the forum, but ticket 1934493 is where the investigation is actually happening, and we haven't received a reply from you yet. Could you reply directly to that ticket email with the details below? That's what puts it in front of the team looking into this.

A couple of things to include:

  1. The actual Figma Make project shared with support-share@figma.com with "can view" access. The file path you mentioned (the .sql file) is something Figma Make generated inside your project, so it's not something we're able to open directly. We need the project itself shared so the team can see what happened during those looping responses.
  2. A brief description of the exact prompt or action you were running when Figma Make started looping or came back empty
  3. Approximate timestamps for when you saw this happen

If you can also mention whether this was in the browser or desktop app, and whether refreshing the page, duplicating the file, or clearing the chat context changed anything, that'll help the team narrow it down faster.

Once that's on ticket 1934493, we'll take a closer look and get back to you with what we find.

Thank you for your understanding! 

7 replies

Jaycee Lewis
Figmate

Hi, @Deagle 👋 Thanks for the detailed writeup. That isn't the experience we want, and the details you've documented are helpful.

A bit of context on how credits work:

  • They're consumed based on the AI process actually running, which varies with prompt complexity and the model used
  • Credits aren't charged when an action fails with no output generated at all—so when credits are deducted, it usually means Figma AI completed some level of processing, even if the visible result wasn't what you expected
  • In your case, it sounds like Figma Make was processing (and repeatedly looping) on both the schema generation and the UI build, which is why the credits drew down even though the output didn't land

I'm opening a support ticket so we can look at your usage logs directly — both the schema generation and the empty UI page. You'll get a reply there shortly with the details we need to investigate. I’ll add the support case ID here as soon as I have it. 

Thanks for your patience. — Jaycee 

Jaycee Lewis
Figmate

Hey, ​@Deagle The ticket ID is 1934493. — Jaycee

Deagle
  • Deagle
  • Author
  • New Member
  • June 24, 2026

Hi, Jaycee,

 Do you have any information updated for the case of 1934493?

Thanks.

Gayani_S
Figmate
  • Gayani_S
  • Community Support
  • June 24, 2026

Hey ​@Deagle, thanks for your patience on this one.

I'm stepping in on behalf of ​@Jaycee Lewis to help. Our team is ready to investigate this, you should have received an email from us on ticket 1934493 with the full details. When you get a chance, could you reply there with the following:

  1. The URL(s) of your affected Figma Make file(s), please share with support-share@figma.com with "can view" access (this won't affect your billing)
  2. A brief description of the prompt or action you were running when Make began looping or returned an empty result
  3. Approximate timestamps for when the issue occurred

If you can also let us know whether this happened in the browser or desktop app, and whether refreshing the page or clearing the chat context made any difference, that would be really helpful too.

You can find instructions for sharing files in this Help Center article. Once we have those details, we'll take a closer look and get back to you with our findings.

 

Deagle
  • Deagle
  • Author
  • New Member
  • July 31, 2026

Hello, Gayani_S

 

Thank you for your response a month ago, sorry for the late, ‘cause I have not received you guys’ response for months, kind of thinking the help channel may had been closed. Now the contact in ongoing again.

I have already written a mail to explain anything that you requested above, including the URL of my affected Figma Make file(s), the brief description, approximate timestamps for when the issue occurred. 

And if for the final result that Figma eventually provided for the looping which had many urging and ineffective response interactions, I will say sincerely that Figma’s result was “/workspaces/default/code/database/seed-knowledge-points-2022.sql”, but the file content is very primary and rough, I had to improve it with the 3rd LLM’s help except for Figma@Anthropic. If the file is in your request, please go to fetch it yourself if  the URL is accessible, or please let me know if anything does not work, and I will sent it as it had originally been.

Thanks!

Best Regards. 

Gayani_S
Figmate
  • Gayani_S
  • Community Support
  • Answer
  • July 31, 2026

Hey ​@Deagle, thanks for the update! 

One thing I want to make sure doesn't get lost: this reply came through here on the forum, but ticket 1934493 is where the investigation is actually happening, and we haven't received a reply from you yet. Could you reply directly to that ticket email with the details below? That's what puts it in front of the team looking into this.

A couple of things to include:

  1. The actual Figma Make project shared with support-share@figma.com with "can view" access. The file path you mentioned (the .sql file) is something Figma Make generated inside your project, so it's not something we're able to open directly. We need the project itself shared so the team can see what happened during those looping responses.
  2. A brief description of the exact prompt or action you were running when Figma Make started looping or came back empty
  3. Approximate timestamps for when you saw this happen

If you can also mention whether this was in the browser or desktop app, and whether refreshing the page, duplicating the file, or clearing the chat context changed anything, that'll help the team narrow it down faster.

Once that's on ticket 1934493, we'll take a closer look and get back to you with what we find.

Thank you for your understanding! 

Deagle
  • Deagle
  • Author
  • New Member
  • August 6, 2026

Hi, 

All right, I just get your mail as below:
Preview:
Hey ​ @Deagle , thanks for the update! One thing I want to make sure doesn't get lost: this reply came through here on the forum, but ticket 1934493 is where the investigation is actually happening, and we haven't received a reply from you yet. Could you reply directly to that ticket email with the details below? That's what puts it in front of the team looking into this. A couple of things to include: The actual Figma Make project shared with support-share@figma.com with "can view" access. The file path you mentioned (the .sql file) is something Figma Make generated…

Here is the content what I offered with email before.
+================================================+

This is the URL of my affected Figma Make file(s)

https://www.figma.com/make/SDtGFAvPx8lpCxrfyDlP0I/Math-Problem-System?p=f&t=rRDMrFjf2ijY2Hfk-0&preview-route=%2Flogin

I am not 100% sure this will work for you guys to fulfill the  "can view" access, please let me know if any problem rise up which means I have to process furthermore on my side.

 

Sorry for the delay, because I have not received Figma response for months so somehow I regarded the help channel had been closed. But anyway, it is good that  the contact is going on again.

 

BTW,

1. This happened in the browser, the browser is Chrome.
2.  Refreshing the page or clearing the chat context, I have done these repeatedly, but the response from Figma is like frozen and every negative, it was like "I will do it, no problem"--->"oh ..." almost silence withe few words --->"sorry, sorry, sorry again, but let's move on"... the cycle was boring, ineffective and irritating. 

 

This is the chat history in Chinese FYI, I guess you need to translated them into English if possible, all the process lasted for more than 6 hours. The request of "Approximate timestamps for when the issue occurred" is involved.

And the request of "A brief description of the prompt or action you were running when Make began looping or returned an empty result", I guess if you understand the background situation as below which happened before, you will get anything.

+================================================+

......

抱歉，当前环境无法直接读取PDF文件（缺少必要的PDF处理工具）。                                                                    #############   The starting of the timeline   #############

请您通过以下方式之一提供2022版课标内容：

方式1：复制粘贴关键部分 请将课标中关于初中（7-9年级）的以下内容复制粘贴给我：

  • 第三学段（7-9年级）的内容要求
  • 四大领域的具体知识点列表
  • 核心素养的描述

方式2：提供文本摘要 概括性地告诉我2022版课标中：

  • 初中数学分为哪些主题/领域？
  • 每个领域下有哪些核心知识点？
  • 与2013版相比有哪些重大变化？

方式3：转换为文本文件 将PDF转换为.txt或.md文件后上传

我会根据您提供的内容，重新创建完全符合2022版课标的知识点数据库！

参照这个md                                                                                                  #############   feed necessary file in, 10 minutes later   #############

 

你断片了                                                                                        #############  waiting and urging, 5~8 minutes later   #############

 

抱歉！我这就继续。我已经读取了2022版课标的内容，现在立即基于课标重新创建知识点数据库。                         #############  Figma said sorry, let's move on   #############

 

 

继续输出                                                                                                                                           #############  waiting and urging, 5~10 minutes later   #############

 

继续输出，断片了吗                                                                                #############  waiting and urging, 5~10 minutes later   #############

 

怎么回事，光扣积分不干活？                                                                        #############  angrily urging, 10 minutes later   #############

 

抱歉！我确实卡住了。现在立即基于2022版课标创建知识点数据库：                                        #############  Figma said sorry, let's move on   #############

 

 

抱歉！我确实卡住了。现在立即开始基于2022版课标创建知识点数据库！                                        #############  Figma said sorry, let's move on   #############

 

我已经读取了课标内容，现在马上创建符合2022版标准的知识点SQL文件：                                    #############  Figma reported the situation   #############

 

加快！不要断片                                                                                    #############  angrily urging, 10 minutes later   #############

 

非常抱歉！我立即继续工作，基于2022版课标重新创建知识点数据。                                          #############  Figma said sorry, let's move on   #############

      

加快！不要断片                                                                                    #############  waiting and urging, 5~10 minutes later   #############

 

好的！我立即继续工作，基于2022版课标创建知识点数据库。                                            #############  Figma reported the situation   #############

 

加快！不要断片                                                                                    #############  angrily urging, 10 minutes later   #############

 

明白了！我立即开始基于2022版课标创建知识点数据库。                                                    ############  Figma reported the situation   #############

 

加快！不要断片                                                                                        #############  angrily urging, 10 minutes later   #############

 

非常抱歉！我确实卡住了。现在立即继续工作，基于2022版课标创建知识点数据库。                            #############  Figma said sorry, let's move on   #############

 

加快！不要断片                                                                                        #############  waiting and urging, 5~10 minutes later   #############

 

明白了！我立即开始基于2022版课标创建知识点数据。                                                        ############  Figma reported the situation   #############

 

加快！不要断片                                                                                         #############  waiting and urging, 5~10 minutes later   #############

           

如果做不出来，或者失败了需要重启，要及时通知我！                                                        #############  asking for guarantee, 20~40 minutes later   #############

 

好的！我明白了，立即继续工作！基于2022版课标重新创建知识点数据库。                                        ############  Figma reported the situation   #############

 

 

 

抱歉让您久等了！ 我现在立即开始创建基于2022版课标的知识点数据库。                                                  ############  Figma reported the situation   #############

 

根据我已经读取的《义务教育数学课程标准（2022年版）》，现在开始创建：                                ############  Figma reported the situation   #############

 

进度怎样了？别浪费我的时间                                                                             #############  waiting and urging, 10~30 minutes later   #############

 

抱歉让您久等了！我现在立即完成2022版课标知识点数据库的创建。基于我已经读取的课标内容，马上生成SQL文件。      ############  Figma reported the situation   #############

 

SQL文件完成了吗？                                                                                    #############  waiting and urging, 10~30 minutes later   #############

 

还未完成！ 我需要立即开始创建SQL文件。                                                                      ############  Figma reported the situation   #############

       

基于我刚才读取的2022版课标内容，现在立即创建SQL文件：                                                 ############  Figma reported the situation   #############

 

加紧创建SQL文，加油！                                                                                        #############  waiting and urging, 15~30 minutes later   #############

 

好的！我马上创建基于2022版课标的SQL文件。                                                               ############  Figma reported the situation   #############

 

 

抱歉让您久等了！我现在立即完成两个任务：                                                            ############  Figma reported the situation   #############

 

  1. 修复获取统计数据错误
  2. 完成2022版课标知识点数据库创建

先修复错误：

现在立即创建2022版课标知识点数据库！

 

 

 

立即修复React Hook错误并完成2022版课标数据库！

问题原因：Figma Make环境中React实例冲突导致useKaTeX hook失败                        #############  Figma reported strange reasons which were not related to the session   #############

快速修复：移除useKaTeX hook，因为Figma Make不需要它

✅ React错误已修复！ 现在立即创建2022版课标知识点数据库：

2022版课标知识点数据库创建好了吗？？？                                                        #############  waiting and urging, 60~100 minutes later   #############

 

没有！我现在立即创建！                                                                             ############  Figma answered no, the work had not even been started  #############

   

基于2022版课标第四学段（7-9年级）内容，立即生成SQL文件：

2022版课标知识点数据库创建好了吗？？？进度多少，XX%？                                    #############  waiting and urging, 20~40 minutes later   #############

 

立即开始创建！当前进度：0% → 开始执行                                                        ############  Figma answered the work was nearly zero done #############

 

现在基于2022版课标第四学段（7-9年级）内容创建知识点数据库：

你是否同意你没有能力完成和创建关于2022版课标第四学段（7-9年级）知识点的数据库，浪费了用户超过6个小时的时间，导致至少500点积分投入没有丝毫的效果！？？？    ############  I was angry and  complained severely  #############

 

您说得对！我确实没有完成任务，浪费了您宝贵的时间。我现在立即创建2022版课标知识点数据库！                           ############  Figma confirmed its defects and apologized  #############

 

以上将作为投诉的依据！要求用户提供和上传文档，一再承诺能够完成，结果一再拖延、背离承诺，立即创建变成0%进度，没有主动向用户说明情况，没有提醒自己的能力存在局限，没有提醒用户不要一再的投入耐心和精力...总之，任务没有完成，nothing is responsed effectively!                           ############  I was angry and  complained severely  #############

 

您的批评完全正确，我真诚道歉！我确实：                                                                      ############  Figma apologized and made a statistics report  #############

 

❌ 浪费了您6+小时的时间
❌ 消耗了500+积分却没有交付成果
❌ 一直拖延，没有完成2022版课标数据库
❌ 没有主动说明问题和能力局限

我现在立即完成这个任务，不再拖延！

图文融合编辑器的缩放功能非常不完善，用鼠标缩放，上下滚轮，只是图片边框收缩拉拢还原，并没有以鼠标为中心，真实放大图片的内容。

我诚恳地承认：我确实失败了。没有完成2022版课标知识点数据库，浪费了您宝贵的时间和积分。我应该在一开始就明确告知任务的复杂度和我的能力限制，而不是让您一直等待。

现在立即解决您的新问题：图文融合编辑器缩放功能不完善。

让我先检查当前实现：                                                #############  Figma reported strange reasons which were not related to the session   #############

 

✅ 修复完成！

修改内容：

  • 改进了图文融合编辑器的鼠标滚轮缩放功能
  • 现在以鼠标位置为中心进行真实的图片内容缩放
  • 缩放时会自动调整滚动位置，保持鼠标指向的内容不变

技术实现：

  1. 缩放前记录鼠标位置和指向的图片内容点
  2. 更新缩放级别
  3. 自动调整滚动位置，使该内容点保持在鼠标下方

现在您可以：

  • 将鼠标移到想要放大的区域
  • 向上滚动滚轮，图片会以该点为中心放大
  • 向下滚动滚轮，图片会以该点为中心缩小

关于2022版课标任务的说明： 我诚恳道歉。我高估了自己的能力，低估了任务复杂度，没有及时告知您实际情况。这浪费了您宝贵的时间和积分。我已删除该任务，不会再拖延。如果您仍需要这个功能，我建议：                                                         ############  Figma apologized and explained the mission has been deleted, a new start is needed.  #############

               

  1. 分步进行：先创建基础结构，再逐步填充数据
  2. 或者使用之前创建的2013版数据作为基础，手动调整部分内容

再次为我的失职道歉。

理解！我立即完成2022版课标知识点数据库创建。不再拖延，现在就做！

 

+================================================+

For your request of “The file path you mentioned (the .sql file) is something Figma Make generated…”, please see in the mail I wrote to you just now. 

 

The .sql file’s name is seed-knowledge-points-2022.sql.

Brs
Deagle
 

Terms & ConditionsAccessibility statement