Figma Weave generation stuck loading: fixes

Order of operations

1. Wait 60 seconds. Large frames legitimately take longer than short component prompts.
2. Check the service state. Our status page records the last known generation state.
3. Cancel once, do not spam. Repeated cancel-and-retry cycles queue duplicate jobs behind the original.
4. Reload the file. A dropped websocket leaves the panel spinning even after the job finished server-side.
5. Try a smaller scope. Select a single frame instead of a whole page.
6. Switch network. Tether to a phone for one test; VPN and proxy interference is extremely common.
7. Clear the plugin cache. Restart the desktop app fully, or use the browser version once to compare.

The desktop-versus-browser test

If the same prompt completes in the browser but hangs in the desktop app, the problem is local cache or an outdated app build — update and restart rather than debugging the prompt.

When credits are consumed by a hung job

Note the timestamp. A job that never returned output but decremented the balance is a legitimate reconciliation case.

Related help

• Generation problems and stuck jobs
• Figma Weave is down or unreachable
• Billing and credit problems