Fixing a broken connection

Find the affected account

Open Integrations and check the connection's status. With several accounts on one integration, confirm which account the failed job used.

A notice in Slack may identify the app and offer a reconnect action. Custom MCP connections that fail remain visible so you can repair them.

Reconnect or update credentials

Use Reconnect where offered and complete the provider's sign-in. For key-based connections, update the credential through the secure form. Reconnect with the intended provider account; changing identity may require a separate connection.

Return to the original thread and retry the work. Reconnecting does not prove that an earlier action completed or that every stopped run resumed.

Connected but missing data

Check these separately:

• The connected account can open the record in the source app.
• You selected the intended organisation, project or store.
• The sharing settings permit your request to use that account or document category.
• The connection has write access if the job needs to change something.

For People with existing access, OpenTag must verify the requesting person's source access. Some group and link permissions cannot be established through this check. Try your own connection for those files.

When several connections fail together

Check provider availability and whether an organisation administrator revoked the app or changed access policy. Do not repeatedly reconnect an unrelated account to work around the problem.

If repair fails, contact support with the integration name, visible error and conversation link. Never send a credential in the support message.