An integration is disconnected

Reconnect GitHub, Linear, Slack or another app when its access expires, is revoked or lacks a permission, and fix MCP servers and API keys.

On this page

Integrations give agents access to your other tools. When one stops working, runs that need it fail on their next call to that tool, and you’ll usually see it marked in Settings → Integrations & MCP.

Symptoms

  • An integration shows as disconnected or with an error in Settings → Integrations & MCP.
  • A run fails with a message that it couldn’t reach GitHub, Linear, Slack or another app.
  • Issue-label triggers stop starting runs, or Slack notifications stop arriving.

Likely causes and fixes

Access expired or was revoked

Apps connected with OAuth can lose access when someone revokes Duun in the app’s own settings, the person who connected it leaves the company, or the app’s admin changes its policies.

  1. Open Settings → Integrations & MCP.
  2. Find the integration and click Reconnect.
  3. Approve access on the app’s site. You’ll come straight back to Duun and see Reconnected.

If the original account is gone, reconnect with an account that will stay, ideally a shared admin or service account.

It’s missing a permission

Each connection has read access and, optionally, write access. If agents can search an app but can’t create or update things in it, write access is off. Reconnect and turn it on. Each write still follows Action approvals, so turning it on doesn’t let agents act without asking.

For GitHub, also check the Duun app is installed on the right organisation and has access to the repos your factory uses.

It’s connected for someone else

Connections have a scope, set in Who can use it: just you, your team, one project, or the whole workspace. A connection scoped to Just me only works in runs you start. Reconnect it with a wider scope if teammates’ runs need it. See Connecting integrations.

An API key was rotated or revoked

Integrations that use an API key, such as Datadog or Supabase, store it as a secret. If the key was rotated at the provider, update it:

  1. Open Settings → API keys & secrets.
  2. Find the secret (for example DATADOG_API_KEY) and choose Rotate.
  3. Paste the new value and choose when to stop using the old one. Running agents pick up the new value on their next command.

An MCP server returns 401 or can’t be reached

If Test connection says Couldn’t reach the server (HTTP 401), the token is wrong or expired. Edit the server, paste a new token (sent as Authorization: Bearer …), and test again. For other errors, check the URL is a full https:// address and the server speaks Streamable HTTP. See MCP servers.

After you reconnect

Runs that failed because of the disconnection don’t retry on their own. Open each one and choose Restart run. Triggers resume immediately.

Still stuck? Contact support with the integration name, a run id that failed, and the Duun-Request-Id if you saw one.

    Type to search the docs, help center and blog.