Skip to main content
Start with the exact message on screen. Check the app version, selected workspace, and whether the colony runs locally or in the cloud; each changes where to investigate.

Startup or sign-in

Setup is taking a long time

The first launch can download runtime dependencies. Select Show details to see the active stage. Keep the app connected while downloads progress. An update may require preparation again. If an error appears, record the stage and message. Reopen the app after fixing a connection problem. Do not delete workspace data as a first troubleshooting step.

The app opens but data does not load

Check the internet connection and sign-in state. If the runtime is still starting, wait for it to become ready. If only one page fails, record that page’s error rather than assuming every service is down.

A second launch does nothing

OpenHive uses a single-instance lock for a profile. Check whether a copy is already running. Bring that window forward, or quit it before launching again.

A colony is waiting or has stopped

Hover over its status indicator and read the latest chat message. Check Automation → Workers before treating a quiet queen as an idle colony. Workers can still be executing. If an action may have succeeded before an error occurred, inspect its destination before retrying—especially an email send or a CRM update.

Model access or credits

For No model is available right now, inspect the selected model, credential validity, available credits, and provider quotas. A missing-key error and an exhausted balance need different fixes. Use Credentials, Settings → AI Model, and the plan badge. Avoid adding unrelated keys as a general repair.

Missing results

The Data tab is empty

The agent may have answered in chat without saving a table. Ask it to save the result with explicit columns, then reopen Data.

Colonies or CRM records are missing

Confirm the selected workspace first. Inspect the original colony for task-specific tables; these are not necessarily shared CRM records.

CRM shows setup

Complete the guided setup or use Explore the CRM anyway when offered. The Developer option to preview setup does not erase the server’s completed setup state.

Browser or credentials

If a browser task fails, inspect the connection badge, extension, and website sign-in separately. See Connect your browser. If a service tool reports missing access, check the exact connected account and its permissions. A provider key may be valid but lack access to a particular resource.

Scheduled work did not produce a result

  1. Expand the schedule under Automation → Scheduler.
  2. Check whether it is enabled and inspect Next fire and Last fire.
  3. Check local-versus-UTC timing and daylight-saving changes.
  4. For local work, confirm OpenHive was running and the computer awake.
  5. Inspect workers, chat, and output for the invoked task.
Do not use Force Run until you know another run is appropriate. See Scheduling.

Email

If Inbox is missing, check whether Email senders is enabled for your workspace. Connecting an account and creating a sending profile are separate setup steps. If a reply has no usable sender, verify the delivery account and its authorization. If attachments are rejected, follow the provider-specific error. If the app reports that a message was already answered, refresh and inspect the existing reply before sending again.

Report a problem

Share the app version, operating system, selected surface, local/cloud execution, exact error, time of failure, and minimal steps to reproduce. Runtime diagnostics are available under Settings → Developer → Runtime logs. Remove tokens, passwords, message contents, and other private data from screenshots and logs before sharing them. Ask for help in Discord.