Start here
Answer these two questions first. They separate a broken connection from a normal limit of the provider.1
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.
2
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.
Messages on the Integrations page
Messages after the sign-in
The provider sends you back to the portal, and the portal shows one of these messages.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.
Slack
The agent gives no answer in a channel
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.My message got no reaction. Did Current receive it?
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.
The agent answers messages that are not for it
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.The connection shows a Slack workspace that is not ours
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.
Slack asked an administrator to approve the app
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.
The agent cannot open a file that I attached
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.
Microsoft Teams
The bot gives no answer at all, in any conversation
The bot gives no answer at all, in any conversation
Check these three things, in this order:
- The Microsoft Teams row shows Connected. The bot needs the connection to find your workspace.
- Your Teams administrator uploaded the app package.
- Your Teams administrator set the availability of the app to Everyone.
The bot gives no answer to a channel message
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.
The bot answered before in this thread, and now it stops
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.
The download reports 'The Teams bot is not configured on this server'
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.
Teams refuses the upload: 'This app has already been submitted in your org'
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.
A file never arrives
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.
SharePoint
A workflow finds no site
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.
A workflow cannot write a file
A workflow cannot write a file
Your connection is from before the write permission. Click Reconnect on the SharePoint row.
Our connection stopped when a colleague left
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.
Notion
A search finds nothing
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.
Current reads an old page but not a new one
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.
Salesforce
request not supported on this domain
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.no client credentials user enabled
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.
invalid_client_id or invalid_client
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.
LOGIN_MUST_USE_SECURITY_TOKEN
LOGIN_MUST_USE_SECURITY_TOKEN
Your org needs a security token for this user. See Get a security token.
INVALID_LOGIN
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.
The connection stopped without a change from us
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.
A Sitetracker sync error each hour
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.
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:- The name of the provider.
- The status badge and the grey line of the provider row.
- The message that the portal or the run history shows.