Figma connection and conflict recovery

Symptom	Action
TypeScript template refuses to run	Build and import the generated manifest from the installation guide.
possible import expression rejected on startup	Rebuild from the current plugin source and replace the installed bundle with the generated files. The document bundle removes ordinary dependency comments and rejects remaining runtime imports. Close the running plugin and open it again. Keep LICENSES.txt with the installed files.
Local development URL rejected during manifest import	Rebuild with FIGMA_DEVELOPMENT=true and FIGMA_UI_ORIGIN=http://localhost:3011. Use the same origin in the local API/panel and test identity client. Do not use a numeric loopback address with a port or a wildcard.
Waiting for the document	Open the installed plugin from Figma Design; a standalone browser tab is not the plugin. Check that plugin/UI IDs, versions and configured origins match. Update both bundles if an older UI rejects replies relayed by Figma’s top window. Local operators can use the bounded connection diagnostics in the installation guide.
Approval expired, consumed or wrong code	Start a new connection. Never reuse another person’s approval URL or share a credential.
Session expired or access denied	Preserve needed draft text privately, reconnect through the browser and recheck membership and language permissions.
Framing blocked	The operator must check the narrow plugin CSP and proxy headers. Normal panel frame protection must remain enabled.
Different values changed on both sides	Inspect design, accepted baseline and current server text; resolve explicitly and create a fresh preview.
Content changed after preview	Refresh current content and repeat preview. The failed atomic save did not partially write translations.
Copy, font, style or variable warning	Relink copies explicitly and use supported uniform text. The plugin never detaches components or substitutes fonts.
Outcome of document application is unknown	Inspect the design before rescanning; do not blindly apply again. Figma Undo affects only the document.
Server save succeeded but layer binding failed	Retry mapping from the saved result, or rescan and relink the affected layer. Do not create a new key to hide the error.
Assistance outcome unknown	Read the existing job in the Assistance panel. No automatic paid retry occurs; an explicit new approval is needed.
Image not ready or quota exceeded	Refresh processing state, remove unused references or ask the operator about storage capacity. Never send a failed image to AI.
Maintenance unavailable response	Keep the draft and retry after maintenance. SDK delivery remains independent of the management interface.

Workflow and permissions · Development installation