Troubleshooting
What to do when something doesn't look right.
The plugin says the key isn't accepted
Keys are replaced when someone rotates them, and the old one stops working at once. Copy the current key from the design system's Bring in your tokens panel, or make a new one under Automate, and paste it into the plugin again.
A sync ran but no pull request opened
That's on purpose when the generated files already match your base branch: there's nothing to merge. Check Changes for the sync. If it says the repository is in sync, the tokens in Figma match what's merged. If you expected a change, check that the plugin published from the right file.
A pull request I closed came back
It only comes back when the tokens change again. Changes are measured against basemode.lock.json on your base branch, so the new pull request describes everything merging it would change, including what was in the one you closed.
"Both become …; one was kept"
Two Figma names turned into the same code name, such as Color/Primary and color-primary. Rename one in Figma so they differ.
A token is missing from the output
A variable whose alias can't be resolved is left out with a warning rather than failing the whole sync. The warning is on the sync in Changes. Fix the alias in Figma, or publish the file that holds its target.
Variables don't sync over Figma's API
Figma only shares variables through its API on the Enterprise plan. On other plans, publish variables with the plugin. Styles still sync over the API on any plan.
The Storybook frame on the shared page is blank
Your Storybook host is blocking embedding, usually with an X-Frame-Options or frame-ancestors header. The Open in a new tab link still works. To show it inline, let your host allow framing from basemode.io.
Lint flags a value we mean to keep
Add basemode-ignore in a comment on the line, and lint leaves it out.
Still stuck?
Send us a message with the design system's name and what you expected. A person will read it.