Troubleshooting & FAQ

Sometimes a step in your workflow doesn't work the way you expect. This page explains what the error messages actually mean and what to do about each one.

How errors show up

When a step in your workflow fails, a popup appears on screen with a warning icon. It tells you which step failed and gives you a plain-English reason, so you don't have to guess what went wrong.

If there's more detail available, you'll see a Technical details section you can click to expand. This shows the raw message from the provider (with anything sensitive removed), in case you want to share it when asking for help.

Common error messages and what to do

"No API key found. Add your fal.ai key in Settings > API Keys before running workflows." You haven't added a key for this provider yet. Go to Settings > API Keys and add one.

"Your <Provider> API key was rejected. Check it in Settings > API Keys." The key you saved isn't valid, either it was typo'd, revoked, or expired. Go to Settings > API Keys, remove the old key, and add a fresh one.

"You are out of <Provider> credits. Top up your <Provider> account, then run again." Your account with that provider has run out of balance. Add credits directly on the provider's site, then run the workflow again.

"<Node name> produced no output. Try a different prompt or model." The model returned an empty reply with no specific reason given (a separate message appears when the safety filter is the identified cause, see below). Try rewording your prompt or switching to a different model.

"LLM: no prompt yet. Type a prompt in the node settings, or enable "Prompt from input" and connect a text-producing node." Your LLM node has nothing to work with. Either type a prompt directly in the node, or turn on "Prompt from input" and connect a node that provides text.

"This request was blocked for possible copyright or likeness reasons. Remove named people, brands, or trademarked characters and try again." The provider flagged your prompt as referencing a real person, brand, or trademarked character. Rewrite the prompt without those references.

"Your content was flagged by the safety filter. Try a different prompt." The provider's safety filter blocked your request for another reason (for example, NSFW or policy-restricted content). Adjust your prompt and try again.

"<Provider> rate limit reached. Try again in a few minutes or reduce concurrent workflows." You're sending requests to that provider faster than it allows. Wait a few minutes, or run fewer workflows at the same time.

"Image is too large (max 2048x2048). Use a smaller image." (or similar, for video/audio) Your uploaded image is larger in dimensions than the model supports. Resize it to fit the stated size and try again. When the provider tells us the exact limit, we show it in the message.

Unsupported file format The file type you uploaded isn't supported by that model. The message will list which formats are supported when that information is available.

"<Node name>: the prompt is too long for this model. Shorten it and run again." Your prompt has too much text for the model's limit. Trim it down and run again.

"...the workflow will retry automatically." or "...Try running the workflow again." The provider had a temporary problem on their end. Some failures like this are retried automatically; others need you to hit run again.

"Generation took too long. Try a simpler prompt or different model." The request took longer than the provider allows. Simplify your prompt, or switch to a faster model.

"<Provider> could not find the requested model or resource. Choose a different model." (exact wording varies by provider) The specific model or resource this step was pointed at is no longer available. Pick a different model in the node's settings.

"The run was cancelled." You (or something you triggered) stopped the run before it finished. This isn't an error. It's just confirming the run was cancelled.

"This workflow could not be found. It may have been deleted." The workflow you tried to run no longer exists.

"<Node name> has no saved data. Save the workflow before running it." You ran a workflow with unsaved changes on this node. Save the workflow first, then run it.

"The workflow has a circular dependency. Remove the loop so data flows in one direction." Two or more nodes are connected in a loop. Rework the connections so data flows in one direction, from start to finish, with no loop back.

"Your account has no active billing period. Contact support to resolve this." / "You have reached your workflow run limit for this billing period. Upgrade your plan or wait for the next period." / "Your subscription is inactive. Check your billing settings." These relate to your 60 Minute Creator plan rather than a provider. Check or update your plan in Settings > Billing. See Limits & Formats for the exact run limits per plan.

"<Node name> generated a result but saving it failed. Try running the workflow again." The step actually worked, but we couldn't save the result. Run the workflow again.

Anything else If a message doesn't match a known cause, you'll still get a clear one-line summary rather than a raw error, plus a note to try running the workflow again.

Checking your API keys before you run anything

You don't have to wait for a run to fail to check a key. Open Settings > API Keys and look at the status pill next to each provider:

• Valid: the key works.
• Invalid: the key was rejected. Remove it and add a working one.
• Not configured: no key has been added yet for that provider.

When you save a new key, it's checked against the provider right away. If it doesn't work, you'll see: "This key is not valid for <Provider>. Check that you copied the full key."

FAQ