Troubleshooting

Quick fixes for nodes, agents, fleets, integrations, memory, budgets and more.

Nodes

A node shows offline or has no green dot: the computer may be asleep, off or disconnected from the internet. Click Refresh status in the Connected Nodes panel.
Agents are running on the wrong machine: open the Connected Nodes panel and click Activate on the node you want.
A node isn’t picking up work: check whether it was Paused.
Provisioning fails or Stripe checkout doesn’t open: allow pop-ups, try another payment method, and check whether you were charged before retrying.
A removed cloud node is still being billed: check whether the subscription was cancelled when the node was removed.

An agent keeps stopping to ask for approval: Autopilot is set to Manual. Change it in the dropdown under the composer.
The agent misses key details: the description is probably too vague. Rewrite it to cover role, trigger, actions, output and rules.
Replies are slow or expensive: lower the Thinking effort or Context size, or leave the model on Auto.
The agent type can’t be changed: this is expected. Chat and Workflow types are fixed after creation, so recreate the agent with the other type.

A fleet shows “0 / 9 running”: check Budgets, Runtime concurrency and node status.
A fleet stopped partway through: a budget limit was probably reached. Fleets stop before the next member starts.
Mockingbird can’t be removed as an orchestrator: this is by design. Mockingbird leads every fleet.

A local server (for example Gmail IMAP) won’t install: npx isn’t installed on the node. See Connecting to a local server in MCP
Gmail authentication fails: use a Google App Password, not your normal password. Your Google account also needs 2-step verification turned on.
A remote server shows as connected, but its tools are missing: reconnect it, then open Tools to check.
Adding a custom server (for example Buffer) fails: check the server URL and authentication details.

A channel test fails: check the connection settings for that channel type, such as the WABA tokens or the WhatsApp QR link. If the connection banner shows a problem, click Restart.
WhatsApp QR disconnects: re-scan the code in WhatsApp Web.
The LinkedIn connection fails or expires: reconnect from Social accounts.

The agent can’t find content in uploaded documents: turn on High quality (vector embeddings) so search works by meaning, not just exact words.
The agent doesn’t remember something it was told: check that Auto-save is on, check the memory Scope (Conversation scope doesn’t carry over between chats), and look in Chat history to see whether the fact was recorded.
The agent remembers something it shouldn’t: delete the memory under Saved memories.
Memory search misses related wording: keyword search is on. Choose an embedding model in Memory → Models. This uses credits.

An agent is stuck waiting: a request is sitting in Activity → Waiting for you. Approve it there or in your linked chat app.

“Budget reached,” and work is blocked: raise the limit or wait for the period to reset.
No budget alerts arrive: Budget alerts are off in Configurations → Notifications.
A wallet top-up or promo code doesn’t show up: refresh the page, then check Recent wallet transactions.
Plan credits ran out mid-month: top up the wallet or upgrade your plan.

Page data looks stale: click Refresh or Sync.
Changes to settings didn’t apply: click Save in Configurations.
A page or feature is missing: it may not be included in your plan, for example extra nodes or team features.

Guide version 2.1.73 · October 2026. Still stuck? Write to service@soika.ai or use the contact form.