> ## Documentation Index
> Fetch the complete documentation index at: https://docs.current.orinlabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> What each message means, and what to do about it.

Find your symptom below. The page goes from the general to the particular. It starts with the messages on the **Integrations** page, then the messages after a sign-in, then the behavior of each provider.

## Start here

Answer these two questions first. They separate a broken connection from a normal limit of the provider.

<Steps>
  <Step title="Read the status badge">
    Go to **Settings** > **Integrations**. Find your provider.

    A green **Connected** badge means that Current authenticates correctly. The problem is then a permission, a channel, or a page, and not the connection. Go to the section of your provider below.

    A red **Needs attention** badge means that Current cannot authenticate. Click **Reconnect**. See [Repair a connection](/connect#repair-a-connection).
  </Step>

  <Step title="Read the grey line below the provider name">
    This line tells you the state of the row in one sentence. The next table gives each message.
  </Step>
</Steps>

## Messages on the Integrations page

| Message                                                              | What it means                                                                                       | What to do                                                                    |
| -------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
| `Not connected.`                                                     | No connection exists for this provider.                                                             | Click **Connect**. See [Connect an integration](/connect).                    |
| `Not configured on this server.`                                     | Your Current server holds no credentials for this provider.                                         | Speak to your Current contact. No button repairs this.                        |
| `OAuth is not configured on this server — connect with credentials.` | Your Current server holds no Salesforce credentials, and the two credential options stay available. | See [Salesforce](/integrations/salesforce#choose-how-to-connect).             |
| `Workspace admins manage integrations.`                              | Your role in the workspace is member.                                                               | Ask a workspace admin to make the connection.                                 |
| **Needs attention** badge                                            | Current cannot authenticate to the provider.                                                        | Click **Reconnect**. See [Repair a connection](/connect#repair-a-connection). |

## Messages after the sign-in

The provider sends you back to the portal, and the portal shows one of these messages.

| Message                                               | Cause                                                                                                                                       | What to do                                                                                |
| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
| `Connection was cancelled at the provider.`           | You clicked **Cancel** or **Deny** on the consent page.                                                                                     | Click **Connect** and give your consent.                                                  |
| `The connection link expired — try connecting again.` | More than 10 minutes passed between **Connect** and your consent.                                                                           | Click **Connect** and complete the sign-in without a pause.                               |
| `Only workspace admins can connect integrations.`     | Your role in the workspace is member, not admin.                                                                                            | Ask a workspace admin to make the connection.                                             |
| `The provider rejected the connection — try again.`   | The provider refused the token exchange.                                                                                                    | Click **Connect** again. If the message comes back, speak to your Current contact.        |
| `Failed to connect the integration.`                  | The sign-in ended in a way that the portal does not name. The provider sent back no authorization, or the address held an unknown provider. | Click **Connect** and start again from the **Integrations** page. Do not use an old link. |

<Note>
  Start each connection from the **Integrations** page. A connect link is valid for 10 minutes. After that, the sign-in fails and Current makes no connection.
</Note>

## Slack

<AccordionGroup>
  <Accordion title="The agent gives no answer in a channel">
    The bot is not a member of that channel. Send `/invite @Current` in the channel.

    Confirm that the channel is public. Current answers in public channels only. Slack delivers no message from a private channel, a group message, or a direct message to the bot.
  </Accordion>

  <Accordion title="My message got no reaction. Did Current receive it?">
    A reaction confirms nothing in Slack. The agent adds no acknowledgement reaction to a Slack message, so a message with no reaction is not a failure.

    Wait for the reply in the thread. If no reply arrives, confirm that the bot is a member of the channel.
  </Accordion>

  <Accordion title="The agent answers messages that are not for it">
    This is correct behavior. In Slack, the agent answers every message of a channel that it is a member of, and it needs no mention.

    Use a dedicated channel for the agent, or remove the bot from the channel with `/remove @Current`.
  </Accordion>

  <Accordion title="The connection shows a Slack workspace that is not ours">
    Slack installed the app in the last workspace that you used. Click **Disconnect**, then **Connect** again.

    Read the workspace name at the top right of the Slack permission page before you click **Allow**.
  </Accordion>

  <Accordion title="Slack asked an administrator to approve the app">
    Your Slack workspace needs an approval for a new app, and Slack made no connection. Wait for the approval, then click **Connect** again.
  </Accordion>

  <Accordion title="The agent cannot open a file that I attached">
    Your connection is from before the file permission. Click **Reconnect** on the **Slack** row.

    The agent also opens at most 5 files for each message, and each file up to 10 MB. The agent names a file that it cannot open.
  </Accordion>
</AccordionGroup>

## Microsoft Teams

<AccordionGroup>
  <Accordion title="The bot gives no answer at all, in any conversation">
    Check these three things, in this order:

    1. The **Microsoft Teams** row shows **Connected**. The bot needs the connection to find your workspace.
    2. Your Teams administrator uploaded the app package.
    3. Your Teams administrator set the availability of the app to **Everyone**.

    The third item causes most of these reports. An app permission policy that blocks the app stops the delivery of the messages, and the installation still looks complete.
  </Accordion>

  <Accordion title="The bot gives no answer to a channel message">
    Mention the bot in the message. Teams delivers no channel message to the bot without a mention.

    Mention the bot again in a thread that it already answered. The bot records a follow-up message of such a thread, and it sends no reply to it. See [When the bot answers](/integrations/microsoft-teams#when-the-bot-answers).
  </Accordion>

  <Accordion title="The bot answered before in this thread, and now it stops">
    The thread needs a new mention. Every channel message that needs an answer carries a mention of the bot.
  </Accordion>

  <Accordion title="The download reports 'The Teams bot is not configured on this server'">
    Your Current server holds no bot credentials. Speak to your Current contact. The app package cannot work without them.
  </Accordion>

  <Accordion title="Teams refuses the upload: 'This app has already been submitted in your org'">
    The app is already in your catalog. Every app package from one Current server carries the same app id, so your organization holds one copy.

    To replace it, your administrator selects the app in **Manage apps** and uploads the new package. Teams accepts a new package only with a higher version number.
  </Accordion>

  <Accordion title="A file never arrives">
    In a direct chat, click **Accept** on the offer. Teams delivers a file of a bot only after your consent.

    In a group chat or a channel, the agent sends no file. Teams supports the offer in a direct chat only. Ask the agent again in a direct chat.
  </Accordion>
</AccordionGroup>

## SharePoint

<AccordionGroup>
  <Accordion title="A workflow finds no site">
    The signed-in account has no access to that site. Give the account access in SharePoint, or click **Reconnect** and sign in with an account that holds the access.
  </Accordion>

  <Accordion title="A workflow cannot write a file">
    Your connection is from before the write permission. Click **Reconnect** on the **SharePoint** row.
  </Accordion>

  <Accordion title="Our connection stopped when a colleague left">
    The connection carried the access of that person. Click **Reconnect** and sign in with an account that stays in the organization, for example a service account.
  </Accordion>
</AccordionGroup>

## Notion

<AccordionGroup>
  <Accordion title="A search finds nothing">
    The page is not shared with the integration. Open the page in Notion, click the **···** menu, then **Connections** > **Add connections** > **Current**.
  </Accordion>

  <Accordion title="Current reads an old page but not a new one">
    Notion gives access page by page. A new page receives no access from the connection. Share each new page with the procedure above.
  </Accordion>
</AccordionGroup>

## Salesforce

<AccordionGroup>
  <Accordion title="request not supported on this domain">
    Give the My Domain URL of your org, for example `https://acme.my.salesforce.com`. The address `https://login.salesforce.com` refuses the client credentials flow.
  </Accordion>

  <Accordion title="no client credentials user enabled">
    The connected app has no Run As user. Ask your Salesforce administrator to open the app, click **Manage** > **Edit Policies**, and give a Run As user to the client credentials flow.
  </Accordion>

  <Accordion title="invalid_client_id or invalid_client">
    Check the consumer key and the consumer secret.

    If your administrator made the app in the last 10 minutes, wait and try again. Salesforce takes up to 10 minutes to make a new app available.
  </Accordion>

  <Accordion title="LOGIN_MUST_USE_SECURITY_TOKEN">
    Your org needs a security token for this user. See [Get a security token](/integrations/salesforce#get-a-security-token).
  </Accordion>

  <Accordion title="INVALID_LOGIN">
    The username, the password, or the security token is not correct.

    A password change cancels the security token. If a person changed the password, get a new token and give both new values.
  </Accordion>

  <Accordion title="The connection stopped without a change from us">
    A password change of the Salesforce user stops a connection that uses an API user. Salesforce cancels the security token at the same time.

    Click **Reconnect** and give the new password and the new token. To avoid this, move to a connected app. See [Choose how to connect](/integrations/salesforce#choose-how-to-connect).
  </Accordion>

  <Accordion title="A Sitetracker sync error each hour">
    The sync runs for every workspace with an active Salesforce connection, and it reads the Sitetracker objects. An org without the Sitetracker package gives an error each hour.

    Tell your Current contact if your org holds no Sitetracker package.
  </Accordion>
</AccordionGroup>

## A workflow reports one error, and the connection stays Connected

This is correct behavior, and it confuses people. The badge answers one question only: does Current authenticate to the provider?

The connection keeps the **Connected** badge when the provider refuses a single request. A refusal of that type tells you about the request, not about the connection. Examples are an interface that your organization disables, a permission that the account does not have, and a rate limit.

The tool that made the request reports the error. The other tools continue to operate. Read the run history of the action for the message of the provider.

## Ask for help

Speak to your Current contact. Give these three things:

1. The name of the provider.
2. The status badge and the grey line of the provider row.
3. The message that the portal or the run history shows.