Processing statuses
Every status label GuruSup Brain shows for content, follow-ups to people, sources, content waiting for your first build, Notion backfills, requests and conflicts, with the tab each one appears in.
Use this page to look up a label. For how to work with these screens, see Follow ingestion, Check source status, My requests and Resolve conflicts.
Where a label has no "What to do" entry, nothing is asked of you.
Content items on Ingest
Admins see these on Ingest. Each row is a piece of content Brain is reading: an upload, a batch of updates from a source, or a single update.
The tabs on Ingest are All, Live, Waiting, Learning, Learned and Failed. The Total, Learning, Learned and Failed tiles count content only. The tab counts also include follow-ups to people.
| Label | Tab | Color | What it means | What to do |
|---|---|---|---|---|
| Queued | Waiting | Grey | Brain has the item and has not started on it. | Nothing. |
| Paused | Waiting | Grey | The item is saved, but there is not enough usage left to learn it. | Nothing. Learning resumes when usage renews or increases. See Usage and limits. |
| Waiting to withdraw | Waiting | Grey | Shown while a withdrawal of the item is pending. | Nothing. |
| Learning | Learning | Grey | Brain is reading the item and adding it to your memory. | Nothing. |
| Learned | Learned | Green | Done. The item is in your memory. | Nothing. |
| Revision accepted | Learned | Green | Counted as learned. | Nothing. |
| Withdrawn | Learned | Green | Counted as learned. | Nothing. |
| Failed | Failed | Red | Something went wrong on our side. Your content is safe. | Nothing. Use Contact support in Details if you want someone to look. |
| Held back | Failed | Red | Brain kept the update out because it did not pass its quality checks. The original is saved. | Nothing. Use Contact support in Details if you want someone to look. |
| No access | Failed | Red | Brain could not read the item in the source. | Reconnect the source, or give GuruSup access to the item, then send it again. See Connector troubleshooting. |
| Not supported | Failed | Red | Brain does not handle this kind of item yet. Nothing is wrong with your content. | Nothing. |
| Not searchable yet | Failed | Red | The item is saved but cannot be searched yet. It failed on our side and Brain retries. | Nothing. Use Contact support in Details if it stays this way. |
An item that is saved and searchable but whose last step failed reads Not ready to answer on the Failed tab. Details says linking it to related pages failed on our side. Brain retries automatically and the team has been alerted, so there is nothing to do on your side.
Details for a source item shows three steps: Received, Learned and Ready to answer. A line above the bar says which step the item is on, for example "Step 2 of 3 · Queued", "Step 2 of 3 · Learning from it" or "Step 3 of 3 · Getting ready to answer". For a batch of updates the line can also read "Done" or "All N failed".
There is no retry button for content. Paused items resume by themselves, and for failed ones Brain has been alerted.
Follow-ups to people on Ingest
Admins also see the questions Brain sent to people on Ingest, one row per person or group. They use the same tabs.
| Label | Tab | What it means | What to do |
|---|---|---|---|
| Pending | Live | The question has not gone out yet. | Nothing. |
| Queued | Live | The question has not gone out yet. This is a different Queued from the one for content, which sits in Waiting. | Nothing. |
| Delivering | Live | Brain is sending it. | Nothing. |
| Delivered | Live | The question reached the person. | If there is no answer, use Try next method. |
| Sent | Live | The question went out. | If there is no answer, use Try next method. |
| Reminder sent | Live | Brain reminded the person. | Nothing. |
| Retry scheduled | Live | Brain will try again on its own. | Nothing. There is no need to switch contact methods. |
| Delivery uncertain | Live | Brain is not sure the question arrived and will try again on its own. | Nothing. |
| Response received | Waiting | The person answered. | Nothing. |
| Waiting | Waiting | Brain has the answer and has not finished with it. | Nothing. |
| Submitting | Waiting | Brain is adding the answer to your memory. | Nothing. |
| Declined | Waiting | The person declined. | Try next method asks through their next contact method. |
| Expired | Waiting | The request timed out without an answer. | Try next method. |
| Retired | Waiting | The request is closed. | Nothing. |
| Delivery failed | Failed | Brain could not reach the person with that contact method. | Try next method. |
| Failed | Failed | Brain could not reach the person this way, or could not add the answer to your memory. Details says which. | If Brain could not reach them, use Try next method. If the answer is saved but not added, nothing: Brain has been alerted. |
| Not supported | Failed | This kind of request is not supported yet. | Try next method. |
Try next method appears on Delivered, Sent, Failed, Not supported, Delivery failed, Declined and Expired. Brain confirms with "Trying the next Contact Method" and the person's name.
A follow-up whose answer is saved but paused for lack of usage shows Paused with the note that it will be added once your usage renews or increases.
Requests as members see them
Members see the requests they started under My requests. It uses the same labels, but the filters are named differently.
| Filter on My requests | Same as tab on Ingest | Contains |
|---|---|---|
| All | All | Every request from the last 90 days, up to 200. |
| Live | Live | Requests still going out or waiting for a reply. |
| Response / closed | Waiting | Answered, declined or expired requests, and answers waiting to be learned. |
| Learning | Learning | Answers Brain is adding to your memory. |
| Processed | Learned | Requests whose answer Brain has learned. |
| Needs attention | Failed | Requests that failed or could not be delivered. |
The counters at the top show Total, Live, Response / closed, Processed and Needs attention. Learning has a filter but no counter.
A card can also show why a request ended: Accepted, Cancelled, Completed, Declined by contact, Expired unanswered, Knowledge withdrawn, Slack contact link removed, Slack contact link replaced, Slack workspace disconnected, Organization deprovisioned or Organization restart.
Members never see the colleague's reply. They see progress only.
Sources and connections on Sources
The badge on a source card, and on each connection in Manage, shows the raw status word. The color follows a fixed rule: green for completed, active, connected and succeeded; red for failed, revoked and error; grey for anything else. Uploaded files show an Uploaded badge instead.
| Status | Color | What to do |
|---|---|---|
active, connected | Green | Nothing. |
needs_reconnect | Grey | Click Manage, then Reconnect, and approve access again. The drawer says This connection needs to be reconnected. |
error | Red | Same as needs_reconnect: Manage, then Reconnect. |
revoked, failed | Red | No Reconnect button appears for these. If the source should be working, contact support. |
degraded, paused, and any other word | Grey | No Reconnect button appears. If content stops arriving, contact support. |
Reconnect is offered only for needs_reconnect and error.
When ingestion is paused for your organization, or in Demo Mode, a banner on Sources says new data cannot be added. Existing sources stay available.
Notion backfill
In the Notion export form (Import a Notion export instead), the section headed Backfill shows the state of your last export upload. The label is what Brain shows first. The raw word appears next to it in a badge, red for failed and grey for the rest.
| Label | Raw status | What it means | What to do |
|---|---|---|---|
| Uploaded | uploaded | Brain has your ZIP. | Nothing. You can click Cancel backfill. |
| Validating archive | validating | Brain is checking the ZIP. | Nothing. You can click Cancel backfill. |
| Importing pages | processing | Brain is bringing the pages in. | Nothing. You can leave the page and click Cancel backfill. |
| Complete | complete | The import finished. | Nothing. |
| Incomplete | incomplete | Some pages did not import. The app adds that a retry is available. | Click Retry unresolved when it appears. |
| Failed | failed | The import failed. | Click Retry unresolved if it is offered. |
| Archive rejected | failed | Brain did not accept the ZIP. The message under the status says why. | Read the message under the status. Contact support if it does not help. |
| Page validation failed | failed | Brain could not validate one or more pages in the export. | Contact support. |
| Cancelled | cancelled | The backfill was cancelled. Pages already accepted are kept. | Nothing. |
Retry unresolved appears on Incomplete and Failed when Brain still has the ZIP. Refresh status updates the panel. A line of counts sits under the status: accepted, deduplicated, stale ignored, unresolved, failed and pages.
Steps and fixes are in Connect Notion and Connector troubleshooting.
Preparing your content before the first build
Before the first build, the sources step in setup, and Home while it reads No sources connected yet, show a line beside the button. It tells you where Brain is.
| Line | What it means | What to do |
|---|---|---|
| "Preparing your content. You can continue while we finish." | Brain is still importing or reading what you connected or uploaded. | Click Continue in setup, or Build my memory on Home. You do not have to wait. |
| "Checking your content…" | Brain is reviewing what you connected. | Wait. |
| "Your source is connected." | A source is connected and no document is ready yet. | Click Continue in setup, or Build my memory on Home. |
| "Your content is ready." | Brain finished checking and at least one document is ready. | Click Continue in setup, or Build my memory on Home. |
| "Brain could not check your content. Your work is safe; contact support for help." | The check failed. | Reload. If it stays, contact support. |
Each uploaded file also shows its own state in the Upload documents panel. See Upload content. A card can show a message when Brain could not prepare an app's content, for example that the app could not read the account, is temporarily unavailable, or hit a problem on our side. The Quickstart lists them with the fix.
A webhook with no content yet does not hold the build back, and neither does a connected Slack with no messages yet. Documents that cannot be prepared are dropped on their own while Brain checks your content. The first build reads a first batch of what is ready, chosen by Brain when preparation has finished, and Brain adds the rest after your memory is active. After the build, items follow the content statuses above on Ingest.
Conflicts
Admins see these under Conflicts. See How conflicts work.
| Tab | Badge on the card | What it means | What to do |
|---|---|---|---|
| Open | None | The sources disagree and Brain cannot tell which is right. | Decide, or use Ask a contact. |
| Awaiting response | Waiting for GuruSup to verify | Your decision is saved as evidence and Brain has not checked it yet. | Nothing. |
| Awaiting response | Waiting for a contact | A colleague has been asked and has not answered. | Nothing. |
| Resolved | None | The case is closed. | Nothing. |
| Dismissed | None | The sources did not really contradict each other. | Nothing. |
Each case also carries a severity badge: critical, high, medium or low, followed by "severity".