Skip to main content
Question

CodeConnect falling back to ignoring my snippet (too many nodes???)

  • April 24, 2026
  • 2 replies
  • 12 views

jonathan.narwold

FIGMA IF YOU ARE READING THIS, I have had a support case open for days and you have not responded. This is critical for my organization.

We’ve created a table component in Figma and published a CodeConnect mapping using what used to be called Figma’s no-parser setup and now appears to just be documented under “template API” (https://developers.figma.com/docs/code-connect/template-api/).

If we look at the snippet in the Figma sidebar, our code snippet shows up just fine, but when we query the MCP server, we get back its own completely-fabricated guess as to what it should be instead of our snippet, including dumping raw Figma props onto our React component instead of the mapped props.

If we only add one row from the table, it works fine. If we add more than that, it fails. My best guess is some sort of size limit that Figma MCP has and then it falls back to something else? I have tried everything I can think of and am at a loss.

2 replies

adamsmasher
Figmate
  • Figmate
  • April 24, 2026

Hi ​@jonathan.narwold,

 

Thanks for your post - I can understand your frustration when you’re limited to just one row at a time, as well as awaiting a response from our team. I found your ticket and raised the priority with our team, so you should hear back soon.

 

In the meantime, is it just this one particular table component? Have you tried removing Code Connect for this component and then reconnecting it? I’m wondering if reconnecting it would clear out whatever is causing the issue so it behaves correctly like other components. 


jonathan.narwold

Thanks SO much for responding. Much appreciated.

Yes, it’s just the one component. It is our most complicated component, so I’m also worried I could run into this with others once we start loading up slots with more nodes.

 

I have tried:

  • Removing & reconnecting (multiple times)
  • Recreating table component and connecting to new version
  • Removing & re-adding my code section by section from the map file, using try-catch to find invisible errors, etc. etc. There’s no consistency to when it behaves and when it doesn’t
  • Looking for alternate MCP methods to call - no other options
  • Almost every other conceivable thing one might think of 😀