I’m noticing with Figma Make I’m almost always having to issue multiple requests for the same action - very often it will confirm a change which has simply not occurred. This is on both design and function, across multiple properties. Example - the header copy on a landing page, getting it to left-align with the other content.
The issue is two fold - one, it says the changes are made, but they are not. Two, I end up having to issue the same request repeatedly showing it that its change is not having the intended outcome.
I’ve tried restarting the MacOS app, I’ve tried resetting the cache, running clean-ups of the code, just doesn’t seem to be helping much. Repeated action commands for the same thing are really slowing down my workflow productivity.
Additionally, I’ve noticed Figma Make just stops mid-update. I have to prompt it to continue or it will just not do so. Not sure how to solve these
Figma Make Not Following Even Simple Instructions, Updates Not Occurring.
ok good chat!
SAME!! I am going through the same thing. Basically looks like the server is done I am having the following errors.
Failed to load resource: net::ERR_CONNECTION_REFUSEDUnderstand this error
vendor-core-31cb22b87b85909a.min.js.br:77 [MultiplayerSession] Joining file version 101 (initial load)
Prototype:1 Access to image at - origin 'https://www.figma.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.Understand this error - Failed to load resource: net::ERR_FAILEDUnderstand this error
/api/mcp/clients?:1 ailed to load resource: the server responded with a status of 404 ()
Hey
Could you confirm whether you’re seeing the same behavior and error message that
First, a couple quick things that might help reset the connection:
- Refresh the page, then try prompting again.
- Duplicate your Figma Make file and test the prompt in the copy.
As a next step, you can also check out these resources for more troubleshooting steps and best practices:
If it’s still not following instructions after that, let’s get this in front of our Technical Quality team for a deeper look. When you can, please fill out this form and include:
- the link to this Forum thread for context
- the link to the affected file
- Can edit access for support-share@figma.com
- a short screen recording of the issue in action.
Appreciate you sticking with this. We’ll keep an eye out for your reply and follow up once the team’s had a chance to review it.
Dear Figma Solutions Team,
I am writing to formally report significant issues with my experience using Figma Make. I began using the tool based on a referral and initial performance met expectations, which makes the subsequent degradation particularly concerning.
At the outset, early prompts were handled accurately and followed specifications as instructed. However, after approximately 50 iterations, the system’s behavior changed materially. Figma Make began to consistently fail at executing even simple instructions, such as aligning toggles or making minor layout adjustments.
More specifically, the tool now routinely:
-
Ignores basic and clearly stated requests
-
Claims fixes or updates have been completed when no visible changes occur
-
Introduces unrequested or random elements
-
Demonstrates further degradation with each subsequent prompt
As the project progressed toward completion, productivity declined sharply rather than improving. The system became increasingly unreliable, which made it unsuitable for finishing professional work. This pattern suggests that Figma Make performs better at the beginning of a workflow but loses effectiveness and accuracy as complexity and iteration increase.
In an effort to resolve these issues, I attempted to use Perplexity AI to help craft more precise prompts and identify potential workarounds. Despite this, the core problem persists: Figma Make no longer produces consistent or reliable output, regardless of prompt clarity.
Expected behavior: Consistent, accurate updates that match the provided instructions.
Actual behavior: Unreliable output that prevents effective project completion.
This raises serious concerns about scalability, reliability, and the long-term viability of Figma Make for real-world, end-to-end use cases. For a product positioned as a productivity and creation tool, this level of degradation near project completion is unacceptable.
I am sharing this feedback in the interest of product improvement and would appreciate acknowledgment of these issues, along with any insight into whether they are known, reproducible, or currently being addressed. The Troubleshooting solutions I’m fully aware, no need to mention.
Sincerely,
Stephen Lewis
Hi
Firstly, a few issues affecting output were fixed last week, so if you haven’t already, try refreshing your file and see if things behave as expected.
For next steps, I’ve opened a ticket on your behalf with our Technical Quality team (case: 1707307) so we can take a closer look and make sure this is addressed.
Please feel free to reply here with updates or any new observations, and keep an eye on the email tied to your Figma account for next steps.
Thanks again for your patience and for helping us improve!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.