Debug Log panel

The Debug Log shows every import event in real time: full payload contents, conversion steps, and errors. Use the Debug Log to inspect what Kanzi Figma Importer did when a transfer fails silently.

Opening the Debug Log

Open the Debug Log from Settings > Show log panel. The Settings button is in the Kanzi Studio plugin header.

The standalone toggle button in the header has been removed. Open the Debug Log from the Settings menu.

Warning

Do not drag the splitter between the main panel and the docked Debug Log. Dragging that divider can crash Kanzi Studio and lose any unsaved work. Keep the default width, and save your project before opening the Debug Log.

Filter dropdown

A filter dropdown next to the toolbar narrows the log to a single category:

  • All: every entry (default).

  • BRIDGE: bridge-server messages.

  • WS-IN: WebSocket packets received from Figma.

  • WS-OUT: WebSocket packets sent to Figma.

  • LOCAL: Kanzi Studio-plugin-internal events.

  • ERROR: error and warning lines only.

What the log shows

Default verbosity includes:

  • Connection events (register_studio, accept_connection).

  • Per-block import lifecycle (start, phases, commit).

  • Conflict resolution decisions.

  • Errors, with stack traces for unhandled exceptions.

Verbose payload diagnostics are off by default to keep the UI responsive. To debug a specific transfer at full verbosity, contact the Kanzi Support Portal.

Reading the log effectively

  • Orange and red lines mark warnings and errors.

  • Per-block IDs: every staged block has a stable internal ID, greppable across the log.

  • [FVC/...] lines: Library Asset pipeline (variables and StateManager).

  • [KZ_BAK] and [KZ_BAK_TINT] lines: texture-bake pipeline.

Copying for bug reports

  1. Reproduce the issue.

  2. Click Copy All and paste the contents into the bug report.

  3. Attach the .kzproj if the issue involves metadata or library state.

See also

Settings

Figma metadata node and re-imports

Troubleshooting