Troubleshooting
Common issues and how to resolve them.
This guide helps you diagnose and fix common issues in Fuser. When something isn't working, start with these quick checks to identify the problem.
Quick Diagnostics
- Node Borders: A red border means a node has an error. An animated malachite border means it's processing.
- Connections: A dashed or red line indicates a connection problem.
- API Keys: Check Settings → Providers. Are all your required provider keys configured and valid?
- Provider Status: Check the status pages for your AI providers (e.g., Fal, OpenAI) to see if they are having an outage.
Errors by name
Fuser surfaces errors with stable, named codes so you can search for the right fix. The most common ones:
| You see | What it means | Fix |
|---|---|---|
| Insufficient credits | Your personal balance — or your workspace's shared pool — hit zero before the request could run. Active node did not execute. | Top up from Billing & Plans (personal) or Workspace Billing (workspace). If Auto-recharge is on, also verify your card is valid. |
| Spend limit exceeded | You're a workspace member and you've hit your monthly cap. The pool may still have credits — they're just gated behind your individual cap. | Ask a workspace Admin or Owner to raise your limit in Workspace Billing → Spend Limits. Otherwise the cap resets on the 1st of the next calendar month (UTC). |
| Quota exceeded | A workspace-level rate or storage quota tied to the plan was exceeded. | Check Workspace Billing. If the workspace is on a Free / archived plan after cancellation, re-subscribe to restore quotas. |
| Storage limit exceeded | Your or your workspace's media storage is full. | Delete unused assets in the Assets library, or upgrade the plan. |
| Forbidden | The endpoint refused the action — typically because the workspace tier doesn't include the feature, the workspace is past its 7-day grace period, or your role doesn't permit the action. | Confirm the workspace is on Teams with an active subscription. If you were just demoted, your role can take up to 5 minutes to propagate — refresh and try again. |
| Not found | The project, folder, team, share, or member you referenced doesn't exist (or you can't see it). | Refresh — someone else may have moved or deleted it. If you know the resource exists, ask the owner to confirm your access via Workspace Settings → Access Audit. |
| Validation error | The input you submitted didn't match the expected shape — wrong format, missing field, value out of range. | The error message names the field and the rule. Common cases: invalid hex color, canvas dimension outside 1–4095, file type the server doesn't accept. |
| Resource already exists | You tried to create something with a name or slug that's taken (workspace slug, team name, member invite). | Pick a different name. For workspace slugs, lowercase letters / numbers / hyphens, no leading or trailing hyphen. |
| Execution failed | The provider returned an error, the model rejected the input, or the inference timed out. | Re-execute. Check provider status. Shorten the prompt or simplify the inputs if it persists. |
| Fetch failed | A network call (typically to a provider) failed. | Check your internet, the provider's status page, and your API key validity. Re-execute. |
| Redemption rate limited | You tried to redeem too many perk codes too quickly. | Wait a few seconds and try again. |
| Internal error | Something unexpected on Fuser's side. | Refresh and re-execute. If it keeps happening, file a bug report — include the error and what you were doing. |
Common Problems & Solutions
Node Execution Issues
Connection Problems
Performance Issues
Prevention & Best Practices
- Test Small: Before running a complex or expensive workflow, test the logic with a simple, low-cost input.
- Document Your Work: Use text nodes to leave notes for yourself or your team about how a workflow is supposed to function.
- Save Regularly: Fuser saves automatically, but creating named versions of important workflows is a good practice.
- Monitor Credits: Keep an eye on your credit balance with your AI providers to avoid interruptions.
Reporting a bug
Fuser has a built-in Bug Report dialog. Open it from the help menu and describe what you saw, what you expected, and what you were doing when it happened. The report is sent to the Fuser team along with non-sensitive context about your session — no canvas content, no API keys, no project data is included.
Getting More Help
If your issue isn't a bug to report, the Fuser community is the best place to get help.
- Join our Discord: For real-time help from the community and the Fuser team.
- Check GitHub Issues: See if your issue has already been reported.
What's Next?
After resolving your issues, get back to building.
- Quick Start - Return to the basics and build a simple flow.
- Building Flows - Apply what you've learned to create more robust workflows.
- Templates - Use a tested, reliable template to avoid common issues.