This Nodespell troubleshooting guide lists common symptoms, their likely cause and the fix, grouped by area. Messages in bold are quoted exactly as Nodespell shows them, so you can search this page for the text you see. Each fix links to the guide that explains the feature in full.
Connections
Section titled “Connections”| Symptom | Likely cause | Fix |
|---|---|---|
| Check input connections appears when you run | An input receives a different media type than it expects, for example an image connected to a video input. | Reconnect the asset to a matching input, or choose Run anyway if it is intentional. See Connections. |
| A socket tooltip says Expects one type, got another | The connected output’s content type does not match the input. | Connect an output of the expected type. Hover a socket to see its Type and Content. |
| Some connections on a node could not be matched to its current inputs or outputs | The node’s inputs changed, for example after a model update. | The original connections are preserved; reconnect the affected ones. |
| Not currently driving. A connection is driving this parameter. | A connection overrides the parameter’s expression or value. | Disconnect the input if you want the typed value or expression to apply. |
Running and credits
Section titled “Running and credits”| Symptom | Likely cause | Fix |
|---|---|---|
| The run control says Up to date | Everything selected already has current results. | To make a new result, open Run options › Plan this run… and set the node to Generate. See Run nodes. |
| A downstream run did not regenerate an upstream image | Runs reuse existing AI takes until you explicitly generate. | Select the upstream node and choose Generate. |
| N nodes need a take first | Upstream AI nodes have no result yet. | Use Generate with & run, or run those nodes first. |
| Not enough credits for this run. | Your balance cannot cover the estimate. | Lower the number of takes, or add credits. See Plans and credits. |
| This team’s shared credits are empty | The Team credit pool is used up; personal credits are not used in Team projects. | Ask the Team owner to top up, or wait for the next refresh. See Team credits. |
| No credit estimate next to Generate | Live estimates are a paid-plan feature. | You can still run. See Plans and credits. |
| The run control shows Retry loading plan | The run plan could not be prepared. The tooltip names the reason, such as A media reference in a prompt is missing. or An input is not ready. | Fix the named cause, then click Retry loading plan. |
| upstream asset upload(s) are missing or failed | An input file did not finish uploading. | Open Failed uploads in the top bar, retry, then run again. |
| Run Map body node directly? | You ran a node inside a Map Container. | Run the Map Container instead. See Data and logic. |
| Folders cannot be run directly. | A Folder is organization only. | Go inside and run the nodes there. See Levels and Folders. |
| A run in Task queue says Waiting for browser or Resume browser session | Part of the run executes in your browser and the tab was closed or reloaded. | Click Resume in Task queue. See Tasks panel. |
| A task failed | The model rejected the input, or an input was missing. | Read the error in the Tasks panel or use Tasks › Copy error on the node, fix the cause, and run again. |
Results and takes
Section titled “Results and takes”| Symptom | Likely cause | Fix |
|---|---|---|
| This take could not be used. The node still uses its previous take. | The change could not be confirmed, for example during a reconnect. | Try Use again once the project is connected. See Takes. |
| Use is unavailable and says Only successful takes can be used. | The take failed or was cancelled. | Choose a successful take, or run again. |
| Wait until the take finishes. | The take is still generating. | Wait for it to complete. |
| You’re viewing this project, so takes can’t be changed. | You are viewing, not editing. | Choose Edit here or Request editing; see Saving and recovery. |
| A take is protected and cannot be deleted | A pinned branch, a saved snapshot, a copy or a running generation uses it. | Remove that reference first, or keep the take. |
| A new run replaced the result you liked | The node follows the latest take. | Open Takes… and click Use on the take you want. The node then keeps it. |
| Some takes couldn’t load. The node keeps its current output. | A connection problem while loading history. | Click Retry loading. |
Saving and recovery
Section titled “Saving and recovery”| Symptom | Likely cause | Fix |
|---|---|---|
| The save status shows Saved locally | Changes are kept on this device and waiting for the server. | Keep the tab open until it shows saved. |
| Editing paused | Too many changes are waiting to save (editing pauses at 99). | Wait for saves to finish; check your connection. |
| Needs attention | Some edits could not be saved. | Open the status to review Unsaved changes: use yours, discard them, or Export for support. See Saving and recovery. |
| Uploads pending | Media is still uploading and is not in the local backup. | Keep the tab open until uploads finish. |
| Your other tab isn’t responding | Another tab or device holds editing for this project. | Choose Keep waiting, or Take over now. |
Assets and uploads
Section titled “Assets and uploads”| Symptom | Likely cause | Fix |
|---|---|---|
| Unsupported file types | The file format is not accepted. | Convert it to a supported format. See Supported media. |
| Files too big or Too many files | The upload is over the size or count limit shown in the message. | Upload fewer or smaller files. See Upload and organize. |
| Assets could not be loaded. | A connection problem. | Check your connection and reopen the Asset Manager. |
Browser and loading
Section titled “Browser and loading”| Symptom | Likely cause | Fix |
|---|---|---|
| Nodespell could not load. Check your connection and try again. | The app could not load. | Click Reload. |
| Nodespell has been updated | A newer version is available. | Click Reload Nodespell to continue where you left off. |
| This panel ran into a problem | One panel failed; the rest of the workspace is unaffected. | Click Try again, or Report this problem with the copied details. |
| Preview not supported in this browser | The browser cannot show that preview. | Try another browser. |
| Keyboard shortcuts do nothing | The graph panel does not have focus, or a text field or menu is active. | Click the graph, then try again. See Shortcuts. |
| Symptom | Likely cause | Fix |
|---|---|---|
| Open a graph panel first. | The Agent needs a graph to work on. | Open a Graph panel, then send the request again. See Agent. |
| Another assistant request is already running in this project. | One Agent request runs per project at a time. | Stop it or wait for it to finish. |
| Turn budget reached | The turn hit its spending limit. | Check Spending limit per turn in the Agent composer, then continue. See Sessions and models. |
| The assistant paused after repeated failures. | The same step failed several times. | Edit the prompt before trying again. |
| This proposal is out of date. | The graph changed after the Agent proposed a change. | Ask the Agent to review the current graph. |
| An attachment is rejected | Over 12 files at once, over 200MB each, or an unsupported type. | Attach fewer or smaller files. See Context and references. |
Frequently asked questions
Section titled “Frequently asked questions”What should I include when I contact support?
Section titled “What should I include when I contact support?”Include the task ID (Copy Task ID in the Tasks panel), the exact error message, and any support code shown. See Support.
Why did my run not spend credits?
Section titled “Why did my run not spend credits?”Nodespell reused existing takes. Only nodes marked Generate in the run plan spend credits.
Will I lose work if saving fails?
Section titled “Will I lose work if saving fails?”Unsaved edits are kept on your device and listed for review, and you can export a copy. Keep the tab open until the status shows saved.
Related
Section titled “Related”- Run nodes: run plans, costs and stopping runs
- Tasks panel: failure details and usage
- Takes: choosing and deleting results
- Saving and recovery: unsaved edits in depth
- Support: getting help