Troubleshooting & FAQ
Fixes for common issues and answers to frequently asked questions.
Common issues
A run gives an empty result
Make the instructions in DO more specific about the task. Check that the neuron's GET inputs have the values you expect before you run it, and that the output type in MAKE matches what you ask the AI to make.
A file upload is rejected
Check that the input takes that kind of file (see Data types), that the file is no larger than 32 MB, and that it isn't damaged or password-protected. Large files take longer to read.
Telegram messages don't arrive
In the neuron's SEND tab, check that Telegram chat shows a connected chat. If it doesn't, click Connect Telegram and press Start in the Neuron bot. See Neuron nodes.
Results don't reach my address (SEND › API)
The Endpoint URL in SEND › API must start with https://, http:// or / and be reachable from the internet; an address on your own computer won't work. Clearing the field turns API off. Recent deliveries under the field shows each result sent, the status your server answered with and whether it will be tried again. If every call is refused by your code, check the signature with the Signing secret shown there; a rotated secret replaces the old one at once. See Webhook integration.
Credits were used but there's no result
AI work uses credits even when a run fails or returns nothing. Find the run on the Usage page, make the instructions clearer, and try again. See Credits & usage.
I can't publish an agent
A workflow can be published only when all its neurons form one connected flow, with no loop and no neuron left on its own. Hover over the greyed-out Publish button to see what needs fixing. See Publishing your agent.
A neuron shows "1 to fix"
The neuron has a problem that stops it running, such as missing instructions or a broken reference. Open the neuron: the tab with the problem is marked, and the issue is shown at the top of it, sometimes with a Fix button. See Neurons.
Play is greyed out
Only one run can go at a time in a workflow. Wait for the current run to finish, or stop it. See Running.
Calls to my neuron's webhook are refused
Open the neuron's webhook panel and look at the Calls tab: each refused call says why. "Rejected: the key or signature was wrong, expired or revoked." means you should check that the API key is active (not revoked or past its expiry date), that it was made for this neuron, and that each call is signed with the key's secret. A call can also be refused because a required input was missing, the webhook is switched off, or the workflow's triggers are paused or the workflow was deleted ("This workflow's triggers are paused. Nothing was run."). Your own application must call the external address under Request; the neuron-to-neuron address is only for calls between neurons, and a call with the wrong kind of key is refused. Webhook integration shows how to send a signed call.
Calls are refused for too many requests
The API key has a rate limit and the calls went over it. Wait, send calls less often, or raise the key's limit on the API Keys page.
A webhook call's status shows failed or timed out
failed means the neuron's run ended with an error: open the neuron and check its result. timed out means the run didn't finish within 1 minute; the run itself may still finish. Try a smaller input or simpler instructions.
A schedule, webhook or app event didn't start my workflow
Check whether the workflow's triggers are paused: its card on My workflows shows Paused, and its canvas shows "Triggers paused." Click Resume triggers in the card's menu, or Resume on the canvas. What came in during the pause isn't run later. A deleted workflow's triggers stop too. See Running.
A run that started without me failed
A run a schedule, webhook or app event started failed. It is listed in Needs you on Home and under the bell, with Fix for a workflow or Open for an agent (opens its History tab). Fix opens the workflow's canvas on the neuron that failed, with a message saying how the run started, when it failed and why; click Dismiss to hide the message. The workflow's card on My workflows shows Run failed or Failing; hover over the badge to see the last error, or click it to open the same neuron. The failure stays in Needs you until the workflow's next run from that start succeeds, or you click Dismiss on the item. Every run, failed or not, is listed under Runs in the canvas. See Home and the app bar.
A workflow is gone from My workflows
It was deleted. Right after Delete, click Undo in the message at the bottom of the page to bring it back; the message stays up if you move to another page. A deleted workflow is removed for good after 30 days. Also check the tab and the search: Drafts, for example, shows only workflows that have never run.
Memory is full
The run finished, but what it should remember wasn't saved. Open Memory and free up space. See Memory.