# Troubleshooting (https://docs.fuser.studio/docs/interface/troubleshooting) 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 [#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 [#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](https://docs.fuser.studio/docs/interface/billing.md#credits) (personal) or [Workspace Billing](https://docs.fuser.studio/docs/teams/workspace-billing.md#workspace-credits) (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](https://docs.fuser.studio/docs/teams/workspace-settings.md#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](#reporting-a-bug) — include the error and what you were doing. | ## Common Problems & Solutions [#common-problems--solutions] ### Node Execution Issues [#node-execution-issues] * **Check API Key**: Does the node require an API key? Ensure it's correctly set up in your settings and that your provider account has enough credits. * **Check Credits**: Open **Settings → Billing & Plans** (personal) or **Workspace Billing** (in a workspace). If you see **Insufficient credits**, that's the issue — top up. * **Check Inputs**: Are all required input sockets (sockets without a default value) connected? Is the input data in the correct format? * **Check Rate Limits**: Have you made too many requests to the provider in a short period? Wait a few minutes and try again. * **Check Provider-Specific Errors**: The AI model itself might have rejected the input. Look for messages about prompt length, content filters, or unsupported features. If you have Auto-recharge enabled, the most common cause is that your card was declined or removed. Auto-recharge silently stops when this happens — your balance ticks toward zero on the next request. * Open **Billing & Plans → Default Payment Method**. If the card is missing or expired, add or update it. * After fixing the card, re-enable Auto-recharge if it shows as off. ### Connection Problems [#connection-problems] * **Check Compatibility**: Data flows from an **output** socket (right side) to an **input** socket (left side). You can only connect sockets of compatible data types (e.g., matching colors). * **Check Node State**: You cannot connect to a node that is currently executing. Wait for it to finish processing. * **Check for Errors Upstream**: A single error in one node will stop the entire downstream flow. Look for a node with a red border and fix the issue there first. * **Try Manual Execution**: Select the node that isn't updating and click the **Execute** button (▶️) in the toolbar to force it and its dependencies to run. ### Performance Issues [#performance-issues] * **Check File Sizes**: Large media files (>50MB) can cause performance problems. Try optimizing or resizing your media before importing. * **Simplify Your Workflow**: Very complex flows with hundreds of nodes can slow down the interface. Consider breaking your work into smaller, more focused flows. * **Check Browser**: Ensure you are on the latest version of a modern browser like Chrome or Firefox. Close unnecessary tabs to free up memory. ## Prevention & Best Practices [#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 [#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 [#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? [#whats-next] After resolving your issues, get back to building. 1. **[Quick Start](https://docs.fuser.studio/docs/interface/quick-start.md)** - Return to the basics and build a simple flow. 2. **[Building Flows](https://docs.fuser.studio/docs/interface/flows.md)** - Apply what you've learned to create more robust workflows. 3. **[Templates](https://docs.fuser.studio/docs/interface/templates.md)** - Use a tested, reliable template to avoid common issues.