ConnectorsTroubleshooting

Connector troubleshooting

Find your symptom, from nothing coming in to failed approvals, reconnect prompts and people who cannot read a source, and follow the fix. Problems that belong to one connector are on its own page.

Find what you see, run the short checklist, and follow the fix. This page is for admins: they manage Sources, and only admins can open Ingest. Members can browse the catalog, read about company sources and upload files. It covers what can happen with any connector. Messages only one app gives, such as a Holded token missing a permission, are in that connector's "If it does not work" section: see Fixes for one connector.

What you seeGo to
A connector is connected but nothing comes inNothing is coming in
A red message when you came back from the appThe connection failed when you came back from the app
A red message starting "Could not connect" in the connect dialogA key or address was not accepted
A red message under an app in setupA problem preparing content in setup
Needs reconnect, Error or "This connection needs to be reconnected."A source needs to be reconnected
A status word you do not knowConnection statuses
A banner saying ingestion is paused, Demo Mode is active, or usage is used upNew data cannot be added
An item on Ingest says Paused, No access, Held back or FailedAn item on Ingest has a problem
Someone cannot get answers from a source, or can when they should notThe wrong people can read a source
Sources will not load, or remove and disconnect failThe page will not load or an action fails

Nothing is coming in

Go down the list. The first "no" is usually the cause.

CheckWhere to lookIf not
The memory is builtSources, Ingest and other pages say "Available once your memory is built" until an admin builds it.Build it. See Quickstart.
No banner holds data backThe top of Sources and of the app.See New data cannot be added.
The connection is healthySources > open its row > the badge under Organization accounts.See A source needs to be reconnected.
You expected new content, not oldMost connectors start from the moment you connect.Bring in past content with Import history (HubSpot, Notion, Holded, ClickUp, Asana, Linear, Granola, tl;dv, Factorial, Zernio, monday.com and Attio) or, for Notion, the page picker under Content while an import runs. Slack, HappyScribe, Sesame, Mintlify and Documentation.AI have none. See How connectors keep Gurusup in sync.
The item reached LearnedIngest, filtered to the source: the badge on the newest item.Paused means you are out of usage. See An item on Ingest has a problem.
You are looking at the right datesIngest shows 30 days by default.Switch to 7d or 90d.
The app lets Gurusup see itEach connector reads only part of the app: the Slack channels the app joined, the Notion pages you shared, the public boards in monday.com.Read What Gurusup reads on the connector's page.

Problems with one connector

Each connector page ends with an "If it does not work" section listing every message it can show.

ConnectorIts fixes
SlackConnect Slack: the channel notice, private channels, an uninstalled app
NotionConnect Notion, plus export refusals and rejected exports
HubSpotConnect HubSpot: importing earlier deals and changes that do not trigger a re-read
HappyScribeConnect HappyScribe
HoldedConnect Holded: token permissions and API calls
ClickUpConnect ClickUp
AsanaConnect Asana
LinearConnect Linear
GranolaConnect Granola
tl;dvConnect tl;dv
FactorialConnect Factorial
SesameConnect Sesame
ZernioConnect Zernio: key permissions
monday.comConnect monday.com
AttioConnect Attio: token scopes
MintlifyConnect Mintlify
Documentation.AIConnect Documentation.AI
WebhookSend data with a webhook: every response your sender can get
Upload filesUpload content: limits and refusals

A connection failed

Nothing is connected after any of these. Fix the cause and start again from Catalog.

The connection failed when you came back from the app

This applies to the apps you approve in the app itself: Slack, Notion, HubSpot and Linear. The app sends you back to Gurusup with a red message that names it:

MessageWhat to do
"OAuth state expired. Start the connection again."The approval link lasts 15 minutes. Start again and finish faster.
"This connection request was not found or was already used. Start the connection again."The link was used already, or the request was cleared. Start again.
"We couldn't match this Slack sign-in to a connection request. Start connecting Slack again." (and the same for the other apps)The return link did not match a request. Start again.
"We couldn't match this sign-in to a connection request. Start the connection again."Start again.
"Access to Slack wasn't granted, so nothing was connected. Start again when you're ready."The approval was declined or cancelled. Start again and approve.
"The connection to Slack didn't finish, so nothing was connected. Start connecting it again."The app sent you back without finishing. Start again.
"The Slack connection changed while you were signing in. Refresh the page and connect again." (Notion says the same with "The Notion connection".)The connection was changed while you approved. Refresh the page, then connect again. Another Gurusup organization using the same account does not cause this.
"We couldn't finish connecting Slack because of a problem on our side. Nothing was connected. Try again in a few minutes, and contact support if it keeps failing."Try again later.
"Integrations can't be changed right now while we finish maintenance on your organization. Contact support if this lasts more than a few minutes."Wait, then contact support.

When the app sends its own description of the problem, Gurusup shows that text instead. "Could not connect" followed by only the app's name means: try again. Messages only one app gives, such as Slack Enterprise installations, are on that app's page.

A key or address was not accepted

This applies to the apps you connect with a key, a token or an address: HappyScribe, Holded, ClickUp, Asana, Granola, tl;dv, Factorial, Sesame, Zernio, monday.com, Attio, Mintlify and Documentation.AI.

What you seeWhat to do
Connect stays offGurusup is still checking what the key or address reaches, or found a problem. Read the message under the field, fix it in the app and paste again.
A red message: "Could not connect" and the app's name, then a reasonFollow the reason. The connector's "If it does not work" section lists every one.
The account is already connectedInside one organization, an app account is one connection: open it on Sources. Another Gurusup organization using the same account does not stop you.
The reason says the problem is on our sideTry again in a few minutes, and contact support if it keeps failing.

A problem preparing content in setup

In setup, and on Home before the first build, Gurusup prepares what each connected app holds. If it cannot, a red line appears under the app:

MessageWhat to do
"(App) could not read this account. Open the connection above to check its permissions or reconnect."Open the app's page, check what you gave Gurusup access to, and reconnect if it asks you to.
"(App) is temporarily unavailable. Your work is safe; preparation will resume automatically when it responds."Nothing. Gurusup tries again on its own.
"We could not prepare your (App) content because of a problem on our side. Your work is safe. We are checking it and preparation will resume automatically; contact support if you need help."Nothing, or contact support if it lasts.

A source needs to be reconnected

On Sources, open its row. The account's badge under Organization accounts reads Needs reconnect or Needs attention. Click Reconnect on the account's row.

AppWhat the dialog asks forWhat to do
Slack, Notion, HubSpot, LinearApproval in the app again.Click Reconnect on the account's row and approve access again in the app. You come back to the page you started from.
HappyScribe, Holded, ClickUp, Asana, Granola, tl;dv, Factorial, Sesame, Zernio, monday.com, AttioA new key or token.Create it as the hint and Show steps say, paste it in the Reconnect dialog and click Reconnect.
Mintlify, Documentation.AIThe address of your published docs.Check the address and click Reconnect.

Reconnecting keeps the connection's knowledge access and saved choices. Until you reconnect, Gurusup reads nothing new from it; what it learned stays. With several accounts of one app, click the name of the one with the problem first. If the app has no row, open Catalog, find it and open its page.

Connection statuses

The badge on a source row and the badge on each account on the source page both use plain words, such as Connected, Syncing, Needs reconnect or Needs attention. Every label is in Processing statuses.

BadgeStored wordWhat it meansWhat to do
Connectedactive, connectedWorking.Nothing.
Needs reconnectneeds_reconnectThe app no longer accepts the connection: access was withdrawn or the key was refused.Click Reconnect, or paste a new key or token.
Needs attentionerrorGurusup could not use the connection.Click Reconnect.
Check delayeddegradedPart of the connection stopped working while the rest still does. For Notion, one of your approvals stopped working.For Notion, click Reconnect on the account's row and approve again. Contact support if content still does not arrive.
DisconnecteddisconnectedThe connection was disconnected.Connect the app again if you need it.
DisconnectedrevokedFor Slack, the app was uninstalled or Slack withdrew its access. Every channel source was closed.Click Reconnect on the account's row on the Slack page, approve, then invite the app to your channels again.
Status unavailableAny other wordNot a state you can act on.Contact support if content stops arriving.

Reconnect is on the account's row on the source page. On a source row, green means working, red means failed, revoked or error, amber means it needs a reconnect, and grey is everything else.

New data cannot be added

A banner on Sources says External ingestion is paused. or Demo Mode is active. Gurusup ignores incoming data and the buttons that add or change content on the source pages are off; Disconnect and Remove source still work while ingestion is paused, but not in Demo Mode. A click on something that is off returns "Ingestion is paused for this organization. Ask your organization admin to resume ingestion before adding content." or "Demo Mode prevents changing external sources. Ask your organization admin to turn off Demo Mode to continue." The full list of what is off is in When ingestion is paused or Demo Mode is on.

Nothing on the page turns this off. When ingestion is paused, the top of the app says "Ingestion is paused for this organization. Your sources aren't being read, so the Brain only knows what it already had." Use Contact us on it and ask about your organization. In a demo account the banner says "You're in a demo account. Contact sales for full access."

Usage used up, or a payment needs attention

These banners at the top of the app also hold new content back, but differently: content is saved and waits. Only admins see them.

BannerWhat it meansWhat to do
It says you have used all of this month's usage and that new content is queued until it renews or you upgradeItems from every connector wait as Paused on Ingest and resume by themselves.Wait for usage to renew, or upgrade. See Plan and usage.
"Ingestion is paused because a payment needs attention. New content stays queued; you can still ask your Brain."A payment needs attention.Open View billing and fix the payment.
"Your subscription renewal is being confirmed. New content stays queued; you can still ask your Brain."A renewal is in progress.Wait for the confirmation.

An item on Ingest has a problem

The full page is Follow ingestion.

BadgeWhat Details saysWhat to do
PausedYour content is saved and learning resumes automatically when your usage renews or is increased enough for the document.Nothing. Every connector uses your usage. See Usage and limits.
No access"We couldn't read this page in" the source, "the connection no longer has access."Reconnect the source. The Reconnect button in Details, for example Reconnect Notion, takes you to Sources. Then change the page in the app again so it is sent.
No access"We don't have access to this in" the source.The connection works but this item is not shared with Gurusup. "Give Gurusup access to it there, then send it again."
Held back"We held this update back because it didn't pass our quality checks. The original is saved."Nothing. Use Contact support in Details if you want someone to look.
Failed"This failed on our side. Your content is safe."Nothing. Use Contact support in Details if you want someone to look.

The wrong people can read a source

Who reads a source in Gurusup depends on its knowledge access, not on permissions in the app. See Restrict a source to specific people.

You seeWhyWhat to do
A member gets no answers from a sourceThe source is Restricted and they are not on its list, or it has Default access and they lack the category.Add them under Knowledge access on the source's page, or grant the category in Members and roles.
An admin gets no answers from a restricted sourceAdmins are not included unless picked.Add the admin to the source's list.
Others still read old knowledge from a source you restrictedRestricting an existing source applies to what arrives after you save.Contact support if earlier knowledge must be hidden. Next time, restrict the source when you connect it.
A source you connected in setup is not restrictedSetup has no knowledge access choice, so everything there starts with Default access.Restrict it from Sources. It applies from then on.
"Could not load knowledge access. Try again before editing permissions."The section did not load.Click Try again.
"Knowledge access could not be saved. Your previous settings still apply; try changing access again."The change was not saved, for example because someone else saved first.Check the settings now shown and change them again.
"Could not load members. Try again before choosing who can read this source."The list of people did not load.Click Try again.

The page will not load or an action fails

You seeWhat to do
"Could not load sources", "Could not load source contribution" or "Could not load source connections"Refresh the page. If it keeps happening, contact support.
"Could not disconnect" or "Could not remove source" followed by a reasonTry again from the source's page. After "Could not disconnect" the dialog stays open, so click Disconnect again. Local Uploads cannot be removed. Contact support if it keeps failing.
"Integrations can't be changed right now while we finish maintenance on your organization. Contact support if this lasts more than a few minutes."Wait a few minutes, then contact support.
"Only organization admins can manage integrations."Ask an admin.

When you contact support

Use Contact us on the banner at the top of the app when it shows, or Contact support in Details for an item on Ingest. Send:

  • The source's name as it appears on Sources, for example Slack · your-workspace, and which connector it is.
  • When you last saw something arrive, or when the problem happened, with your time zone.
  • The exact message Gurusup showed, including any text after "Could not".
  • Whether a banner says ingestion is paused.
  • For a webhook, the HTTP status and body your sender got. Do not send the webhook URL, your signing secret or any API key.