Understand GurusupProcessing statuses

Processing statuses

Every status label Gurusup shows for content, sources, requests to people and conflicts, with the tab each one sits in and what to do.

Most labels are on admin pages; members see their own requests under My requests. 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 Gurusup is reading: an upload, a batch of updates from a source, or a single update.

The tabs on Ingest are All, Waiting, Learning, Learned and Failed. The Total, Learning, Learned and Failed tiles, and the count next to each tab, count content only. Follow-ups to people appear in the list but are not counted.

LabelTabColorWhat it meansWhat to do
QueuedWaitingGreyGurusup has the item and has not started on it.Nothing.
PausedWaitingGreyThe 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 withdrawWaitingGreyThe item was deleted at its source, and Gurusup is about to remove the knowledge that relied only on it.Nothing.
LearningLearningGreyGurusup is reading the item and adding it to your memory.Nothing.
LearnedLearnedGreenDone. The item is in your memory.Nothing.
Revision acceptedLearnedGreenCounted as learned.Nothing.
WithdrawnLearnedGreenGurusup removed the knowledge that relied only on this item. Facts other sources also back stay. Counted as learned.Nothing.
FailedFailedRedSomething went wrong on our side. Your content is safe.Nothing. Use Contact support in Details if you want someone to look.
Held backFailedRedGurusup 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 accessFailedRedGurusup 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 supportedFailedRedGurusup does not handle this kind of item yet. Nothing is wrong with your content.Nothing.
Not searchable yetFailedRedThe item is saved but cannot be searched yet. It failed on our side and Gurusup retries.Nothing. Use Contact support in Details if it stays this way.

An item that was still queued when its source was disconnected is cancelled. It is not learned and costs no usage, and what Gurusup learned earlier stays. An assistant reports it to an admin as Inactive, with "This content was not added because its source was disconnected. Previously learned content is still available."

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. Gurusup 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 the team has been alerted.

Follow-ups to people on Ingest

Admins also see the questions Gurusup sent to people on Ingest, one row per person or group. They use the same tabs.

LabelTabWhat it meansWhat to do
PendingAll onlyThe question has not gone out yet. A call can wait here until a set time: the person is on a call, it is outside their contact hours, or Gurusup spaces out contact. The app shows no reason. The assistant of whoever asked gives it, with the time in UTC.Nothing.
QueuedAll onlyThe question has not gone out yet. This is a different Queued from the one for content, which sits in Waiting.Nothing.
DeliveringAll onlyGurusup is sending it.Nothing.
DeliveredAll onlyThe question reached the person.If there is no answer, use Try next method.
SentAll onlyThe question went out.If there is no answer, use Try next method.
Reminder sentAll onlyGurusup reminded the person.Nothing.
Retry scheduledAll onlyGurusup will try again on its own.Nothing. There is no need to switch contact methods.
Delivery uncertainAll onlyGurusup is not sure the question arrived and will check again on its own. For a call it checks up to three times, then stops (see Failed).Nothing.
Response receivedWaitingThe person answered.Nothing.
WaitingWaitingGurusup has the answer and has not finished with it.Nothing.
SubmittingWaitingGurusup is adding the answer to your memory.Nothing.
DeclinedWaitingThe person declined.Try next method asks through their next contact method.
ExpiredWaitingThe request timed out without an answer.Try next method.
RetiredWaitingThe request is closed.Nothing.
Delivery failedFailedGurusup could not reach the person with that contact method. For a call, this includes a number saved without a country code: Gurusup does not call it.Try next method. If the number is the problem, an admin adds the country code in Contacts.
FailedFailedGurusup could not reach the person this way, could not add the answer to your memory, or could not confirm a call. Details says which. For a call it could not confirm, the reason reads "We couldn't confirm the call went through. Automatic follow-up has stopped." and the event is labelled Call unconfirmed.If Gurusup could not reach them, use Try next method. If the answer is saved but not added, nothing: the team has been alerted. If the call could not be confirmed, there is no Try next method: another request could contact the person twice, so contact support if you need help.
Not supportedFailedThis 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, except on a call Gurusup could not confirm. Gurusup 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 requestsSame as tab on IngestContains
AllAllEvery request from the last 90 days, up to 200.
LiveNone. Ingest has no Live tab; these requests sit under All.Requests still going out or waiting for a reply.
Response / closedWaitingAnswered, declined or expired requests, and answers waiting to be learned.
LearningLearningAnswers Gurusup is adding to your memory.
ProcessedLearnedRequests whose answer Gurusup has learned.
Needs attentionFailedRequests 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 row on Sources and the badge on each account on the source page use the same plain words. A source row and an account can show Connected for active, connected, completed and succeeded, Syncing while a source imports or processes, Needs reconnect, Needs attention for error and failed, Check delayed for degraded, Disconnected for revoked and disconnected, Setup needed and Pending. A source that is not connected reads Not connected. Any other status shows Status unavailable.

Stored statusWhat to do
active, connected (Connected)Nothing.
needs_reconnect (Needs reconnect)Open the source's page and click Reconnect on the account's row. Approve access again, or for a key or token app paste a new one in the dialog.
error, failed (Needs attention)Same as needs_reconnect: click Reconnect on the account's row.
revoked (Disconnected)Click Reconnect on the account's row. Contact support if that does not help.
disconnected (Disconnected)The account no longer has a row. Connect the app again from its page if you need it.
degraded (Check delayed), paused, and any other word (Status unavailable)If content stops arriving, contact support.

The Reconnect button sits on the account's row on the source page. It does not depend on the badge.

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

On the Notion page, the Import from Notion card under History shows the state of your last export upload. The label is what Gurusup shows first, with the counts under it. A badge beside it reads Syncing while pages import and Needs attention when the import failed, and repeats the label otherwise.

LabelRaw statusWhat it meansWhat to do
UploadeduploadedGurusup has your ZIP.Nothing. You can click Cancel import.
Validating archivevalidatingGurusup is checking the ZIP.Nothing. You can click Cancel import.
Importing pagesprocessingGurusup is bringing the pages in.Nothing. You can leave the page and click Cancel import.
CompletecompleteThe import finished.Nothing.
IncompleteincompleteSome pages did not import. The app adds that a retry is available.Click Retry unresolved when it appears.
FailedfailedThe import failed.Click Retry unresolved if it is offered.
Archive rejectedfailedGurusup did not accept the ZIP.Export again as Markdown & CSV, using the steps in Connect Notion. Contact support if it does not help.
Page validation failedfailedGurusup could not validate one or more pages in the export.Contact support.
CancelledcancelledThe backfill was cancelled. Pages already accepted are kept.Nothing.

Retry unresolved appears on Incomplete and Failed when Gurusup 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 Gurusup is.

LineWhat it meansWhat to do
"Preparing your content. You can continue while we finish."Gurusup is still importing or reading what you connected or uploaded.Click Continue in setup. You do not have to wait. After setup, Gurusup starts the build by itself.
"Checking your content…"Gurusup is reviewing what you connected.Wait.
"Your source is connected."A source is connected and no document is ready yet.Click Continue in setup. After setup, Gurusup starts the build by itself once a document is ready.
"Your content is ready."Gurusup finished checking and at least one document is ready.Click Continue in setup. After setup, Gurusup starts the build by itself.
"Gurusup 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 Gurusup 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 Gurusup checks your content. The first build reads a first batch of what is ready, chosen by Gurusup when preparation has finished, and Gurusup adds the rest after your memory is active. After the build, items follow the content statuses above on Ingest.

Conflicts

Admins and members see these under Conflicts, members only for the conflicts they can read. See How conflicts work.

TabBadge on the cardWhat it meansWhat to do
OpenNoneThe sources disagree and Gurusup cannot tell which is right.Decide, or use Ask a contact.
Awaiting responseWaiting for Gurusup to verifyYour decision is saved as evidence and Gurusup has not checked it yet.Nothing.
Awaiting responseWaiting for a contactA colleague has been asked and has not answered.Nothing.
ResolvedNoneThe case is closed.Nothing.
DismissedNoneThe sources did not really contradict each other.Nothing.

Each case also carries a severity badge: critical, high, medium or low, followed by "severity".