Skip to main content

Troubleshooting

Start with the visible status text in Row-Bot. Then check the relevant Settings tab and Monitor. Most issues fall into one of four categories: setup is incomplete, a provider or tool is disabled, the wrong model is selected, or Row-Bot is waiting for approval.

Setup Problems​

  • Reopen Setup Center if first launch was skipped or incomplete.
  • Check Settings -> Providers and Settings -> Models before troubleshooting Chat.
  • Check Settings -> System if local files, browser automation, command execution, or tunnels are involved.
  • For native application control, open the Computer Use setup card and resolve its driver or operating-system permission status before retrying.

Model Problems​

  • Refresh Providers, then refresh Models.
  • Choose a tool-capable model for workflows, Designer, Developer, and multi-step tool use.
  • For local and custom endpoints, use enough context for Row-Bot's instructions and tool schemas.

Chat And Tool Problems​

  • Check the model picker, Agent Profile, approval mode, and enabled tools.
  • If an action is waiting, review the thread approval prompt or open Activity Center.
  • Ask Row-Bot to explain the last tool result if the transcript is unclear.
  • If Computer Use is paused, choose Resume only after reviewing the target; if its lease is busy, stop or finish the active native task first.

Workflow Problems​

  • Confirm the workflow is not paused.
  • Run it manually once before trusting a schedule.
  • Check delivery defaults and channel status.

Designer And Developer Problems​

  • Designer: add a clearer goal, audience, references, or brand details.
  • Developer: confirm a workspace is open before asking for code actions.
  • Review commands and patches before approving or importing changes.

Knowledge And Monitor Problems​

  • If Knowledge is empty, enable memory or index documents.
  • If a record is wrong, edit or remove it.
  • Use Monitor logs, extraction journal, dream journal, and View Full Log for background issues.

Integrations​

  • Channels need credentials, optional tunnel setup, start/stop state, and user pairing.
  • MCP needs the global switch, a trusted server, and a successful test.
  • Plugins need installation, enablement, configuration, and sometimes a restart.
  • Skills need to be enabled and relevant to the prompt.

Voice And Buddy​

  • Check microphone/output device selection and permissions.
  • Use Dictate before Talk if you need review.
  • Check provider readiness for realtime voice.
  • Toggle Buddy visibility or reopen the overlay if the companion is missing.