Most failed connections come down to four things: AI connections are still off in the workspace, the sign-in took longer than 10 minutes, the account has no password, or a send is waiting for your approval. Find the message you saw below.
Almost every fix ends the same way: start the connection again from your AI app. The sign-in page can't be retried on its own, because each connection request can be used once.
The workspace isn't listed, or the page says AI connections are off
AI connections are off in every workspace until the account owner or an admin turns them on. Only workspaces where they are on appear under Choose a workspace.
- "AI connections are off in this workspace", or the workspace shows the label AI connections are off. If you are the owner or an admin, open Settings, then under AI choose AI connections and turn on Allow AI connections. Then choose Reload on the sign-in page. If you aren't, ask the account owner to turn it on.
- "AI connections are off in every workspace you belong to". Same fix: the owner of each workspace you want to connect turns on Allow AI connections.
- "Create your Workspace369 workspace". You chose Continue with Google, and that Google account has no workspace yet. Choose Start a free trial with this account, create the workspace in the new tab, turn on AI connections, then come back and choose I’ve created my workspace. Signed in with the wrong account? Choose Switch account.
See Enable MCP and manage connected apps for the admin settings.
"This request expired"
A connection request is valid for 10 minutes from the moment your AI app opens the sign-in page. If you created a workspace, reset a password or waited for a code in the meantime, the request may have run out. Start the connection again from your AI app.
You can't sign in
- You normally sign in with Apple. The sign-in page offers Google or a Workspace369 email and password, not Apple. Choose a password first: in the Workspace369 app open Settings, then your account page, and choose Reset password by email. Then sign in with that email and password.
- "An account with this email already exists with a different sign-in method." Your account was created another way, such as with Apple or an email and password. Sign in with your email and password, or set a password first as above.
- "That email or password is not correct." Check the email, or choose Reset password by email in the app.
- "The Google sign-in window was closed before it finished. Try again." Choose Continue with Google again and finish in the window that opens. If you are sent to a Google page instead, finish there and you come back to the sign-in page.
- "That code expired. Choose "Send a new code" to get another." Choose Send a new code and enter the new one.
- "That verification code is not correct." Check the code in the text message sent to your phone and enter it again.
- "This account requires two-factor authentication, but no second factor is enrolled." Sign in to the Workspace369 app and finish setting up two-factor authentication, then connect again.
- "Too many attempts. Wait a few minutes and try again." Wait, then try once more.
- "Network error reaching the sign-in service." Check your internet connection and try again.
- "That account has been disabled." Contact support.
- "Could not sign in" followed by a code in brackets. Contact support and include the code.
Approving fails
Each of these sends you back to your AI app, because the request was used up when you chose Approve access:
| Message | What happened | What to do |
|---|---|---|
| Choose a workspace | No workspace was selected. | Start again and pick one under Choose a workspace. |
| Choose at least one permission | Every area was set to None. | Start again and leave at least one area at View or higher. |
| You're not a member of this workspace | The account you signed in with doesn't belong to that workspace. | Sign in with the account that does, or ask the owner to invite you. |
| This page is out of date | A second connection was started in the same browser, so the older page can't be approved. | Close the older tab and use the newest one, or start again. |
| This request couldn't be approved | The permissions sent didn't match what the app asked for. | Start again from the app. |
| Something went wrong | The connection couldn't be finished. | Start again. If it keeps happening, contact support with the app's name and the time. |
Connected, but the app says something is waiting
- A send is awaiting approval. Sending an invoice, proposal or contract, replying to a lead, or texting a client reaches a real person, so a connected AI app's send waits for your approval in the Workspace369 app. Approve it there. The app shouldn't retry it. To let one connection send without waiting, turn on Send without asking for it; see Connect AI apps with MCP.
- The app lacks a permission. You set that area to a lower level when approving, or your role doesn't include it. Disconnect the app and connect it again to grant more.
- Your first workspace disappeared after you connected a second one. Apps identify a connection by its URL. Use the workspace-specific URL for the second one, as described in Connect a second workspace.
- The app is rate limited, or out of AI usage. One connection may make 120 calls a minute and a workspace 600. See If something does not work for AI usage and the other cases.
Still stuck
Start from the beginning with Connect an AI app to your workspace. It has the server URL, the steps for each kind of app, and the permission levels.