Skip to main content
Each connector tile shows its status at a glance. This page explains the statuses, how to get a connection healthy again, and what disconnecting does.

​
Connector statuses

A connection counts as live unless the provider reports a credential or authorisation problem.
Hive does not yet show a “last synced” time on connector tiles. To force a fresh read, ask an Admin to press Run loop now on the Signals or Integrations page.

​
Fix a connection

1

Reconnect

Select the tile and sign in to the provider again. Reconnecting the same account refreshes it rather than adding a new one.
2

Check access in the provider

Make sure the account still exists, still has access to the data, and that an administrator on the provider side has not revoked Hive’s app.
3

Check provider-specific settings

For PostHog, the region must match your project. For Sage 200, the account needs API access and Company Access. See Connect an app.
If a signal source is having trouble, the Signals Coverage tab shows it, so an empty feed is never mistaken for an all-clear. See Coverage.

​
MCP server and webhook status

  • MCP servers show Live when connected, Authorizing while OAuth is pending, or an error. Resync re-discovers the server’s tools. See MCP servers.
  • Incoming webhooks show Awaiting events until the first signed event arrives, then Receiving. See Incoming webhooks.
  • Slack and Teams channels show as active, needing re-authorisation, or disconnected. See Slack and Teams.

​
Disconnect a tool

Open the tile and choose to disconnect. Hive confirms first: “Hive will stop reading from it. Nothing you have already approved is undone.” When a provider has several accounts, the prompt says all of them are removed and Hive stops reading from every one. When you disconnect a managed connector:
  • Hive deletes the connection and stops reading from the account.
  • Every open signal the account was feeding is dismissed, and their pending approvals are removed, so nothing can act through an account that is gone.
  • Actions that already ran are not undone. Undo reversible ones from the audit log if you need to.
  • Each account is revoked separately. If one fails, the others stay connected and you can retry.
Only the member who owns a connection can disconnect it. For other connection types:
  • MCP server — its pinned tools and all stored secrets are deleted, and the connection is marked Disconnected.
  • Incoming webhook — delete it; the URL stops accepting events.
  • Channel — the installation is revoked. For Teams, the app and consent on the Microsoft side remain until you remove them there.
Disconnecting does not delete information Hive already learned from the tool — for example facts in the Business Brain or files already indexed. Contact support if you need data removed. See Data protection.

Troubleshooting

Fixes for common problems.

Accounts and autonomy

Ownership and levels.