Lovelace Developer Portal
Overview
Auth Hub
Studio
Agents Cloud
Skills
Memory Platform
Lattice Cloud
Hosting
Ada CLI
MCP Gateway
Ada
Periscope
Editor Extensions
Skip to main content

Troubleshoot Ada Connected Apps

Start with what the user sees. Ada app problems fall into four groups: the app was connected in the wrong place, Ada is not allowed where the request happened, Ada cannot identify the person, or the team expects disconnect to delete Lovelace history.

Ada Was Connected In The Wrong Place

AppWhat to check
SlackConfirm the Slack workspace name, then disconnect the wrong workspace and connect the right one.
LinearConfirm the Linear workspace name before testing in an issue.
GitHubConfirm the organization and selected repositories.
DiscordConfirm the Discord server and channel where Ada was added.
EmailConfirm the message was sent to the correct Ada email address.

Ada Does Not Answer

AppWhat to check
SlackTry a direct message, then check whether Ada is allowed in the channel where it was mentioned.
LinearMention Ada again in a new issue comment in the connected workspace.
GitHubConfirm Ada is installed for that repository and mention Ada in a new issue or pull request comment.
DiscordCheck whether Ada commands or mentions are allowed in that channel for that role or user.
EmailConfirm the message reached Ada's address and check spam or filtering rules.

Ada Asks For An Account Connection

This means Ada needs to know which Lovelace account belongs to the Slack, Linear, GitHub, Discord, or email profile making the request.

Ask the person to follow Ada's connection prompt. If the person recently changed accounts, switched workspaces, or uses multiple accounts in the outside app, reconnect the profile.

Ada Answers In One Place But Not Another

Check app-specific access:

  • Slack channels allow or block apps.
  • Linear issues must be in the connected workspace.
  • GitHub repositories must be selected for Ada.
  • Discord channels allow or block commands by channel, role, or user.
  • Email replies depend on who was included on the latest message.

Disconnect Did Not Delete Lovelace History

This is expected. Disconnecting an outside app removes that app's access path. Lovelace-owned conversations, Library resources, and account history remain available in Lovelace.

What To Collect For Support

Ask for:

  • the Lovelace workspace name
  • the outside workspace, server, organization, repository, or email address
  • where Ada was asked for help
  • whether Ada answered anywhere else
  • whether Ada asked for an account connection
  • whether the issue started after reconnecting or changing permissions

Related

  • Connect Ada to apps
  • Account connections
  • Manage Ada app connections
  • Data and history

Build and deploy AI agents with ease.

Quick Start

  • Getting Started
  • Build Your First Agent
  • Platform Concepts
  • Examples & Tutorials

Develop

  • Create an Agent
  • Connect an MCP Server
  • API Reference
  • CLI Tools

Platform

  • Agents Cloud
  • Roadmap
  • Platform Changelog
  • Status

Resources

  • Discord
  • GitHub
  • Support
  • Developer Blog
Lovelace logo
Lovelace
Made with ❤️ by Reasonable Tech CompanySupport
TermsPrivacy
All systems operational

Overview

Quickstart

Connect Apps

Slack

Linear

GitHub

Discord

Email

Account Connections

Manage Connections

Data & History

Troubleshooting

Ada